Closed Bug 1530720 Opened 5 years ago Closed 5 years ago

[ARM64] Water WebGL demo crashes at launch on aarch64 build

Categories

(Core :: Graphics: CanvasWebGL, defect, P3)

ARM64
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox66 --- affected
firefox67 --- affected

People

(Reporter: danibodea, Unassigned)

References

(Blocks 2 open bugs)

Details

Note

  • Tab instantly crashes when opening a WebGL water demo website.

Affected versions

  • Nightly v67.0a1 (64-bit) (aarch64 build)
  • Beta v66.0b11 (64-bit) (aarch64 build)

Affected platforms

  • Windows 10 v1803 on Lenovo Yoga

Steps to reproduce

  1. Open http://madebyevan.com/webgl-water/
  2. Follow through the menu, log in with Guest and reach the actual game-play.

Expected result

  • The web application is loaded and functions correctly.

Actual result

  • The tab crashes.

Additional notes

  • This issue does not occur on the non-aarch64 build, including the normal 32-bit build running on Lenovo Yoga, ARM laptop.
  • This water demo works PERFECTLY on Nightly 32-bit (non-aarch build, generic build) on Lenovo Yoga with ARM processor, while it flickers severely on my desktop station (which is a considerably faster system than Yoga) and crashes any aarch64 build at launch.
Summary: [ARM64] Water WebGL demo crashes at lunch on aarch64 build → [ARM64] Water WebGL demo crashes at launch on aarch64 build

Can you link to the crash report?

Flags: needinfo?(daniel.bodea)
Priority: -- → P3

This issue reproduces on Build ID: 20190227202322 and this is the crash report:
https://crash-stats.mozilla.org/report/index/b1ecc48b-1f71-4098-8e49-9323f0190301

The crash does NOT occur on the latest, Build ID: 20190301012442.

Please tell me if you need more investigation. Thanks.

Flags: needinfo?(daniel.bodea)

This issue does not reproduce anymore.
Tested on aarch64 builds on Lenovo Yoga, Nightly v67.0a1 from 2019-03-12, Beta v66.0b14 and RC v65.0.
Marking as WORKSFORME.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

FYI, the crash report in comment #2 is already tracked by bug 1515387 which is not fixed yet, should this bug be duped to that one?

You need to log in before you can comment on or make changes to this bug.