Open Bug 1367417 Opened 7 years ago Updated 2 years ago

After the Flood WebGL 2 demo crashes on Google Pixel XL

Categories

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

55 Branch
ARM
Android
defect

Tracking

()

People

(Reporter: jujjyl, Assigned: jnicol)

Details

(Whiteboard: gfx-noted)

Running After the Flood demo in sequence of URLs

http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=low_sky&hidemenu
http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=aa_2&hidemenu
http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=medium_shadows&hidemenu
http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=verylow&hidemenu
http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=verylow_high_shadows&hidemenu
http://clb.demon.fi/t/2017-02-08-AfterTheFlood/?quality=medium&hidemenu

is crash prone when run on

 - Google Pixel XL - Android 7.1.2, Kernel 3.18.31-g416bf43 (marlin N2G47O), Fennec 55.0a1 (2017-05-19) - Qualcomm Adreno 530, OpenGL ES 3.2 V@145.0 (GIT@Idb2b4cb785)

Sometimes browser crashes on the very first visit, other times reloading the page couple of times seems to be needed. Occassionally the crash did not occur on page load, but when switching Android activities and returning back to Firefox browser that was running the demo page.

Testing on the following devices did not crash:
 - Samsung Galaxy S7 Edge SM-G935F - Android 7.0, Kernel 3.18.14-11104523 (NRD90M), Fennec 55.0a1 (2017-05-19), ARM Mali-T880, OpenGL ES 3.2 v1.r12p1-03dev0.228ab63cced004f840e7dd47b762a1d0
 - Huawei P10 Plus - Android 7.0, Kernel 4.1.18-gfd75bbb (VKY-L29), Fennec 55.0a1 (2017-05-19) - ARM Mali-G71, OpenGL ES 3.2 v1.r2p0-02dev0.f7269486f3e0e3b308edf85872e361f4

The phone did record crash stats, but for some reason does not want to send them to crash stats server (bug 1366716). I'll update here once that bug is resolved.
Whiteboard: gfx-noted
Crashes occasionally on my Pixel (non-XL).

https://crash-stats.mozilla.com/report/index/564ed896-66de-4ea7-b886-18eb20170801

Looking in to it.
Assignee: nobody → jnicol
QA Whiteboard: qa-not-actionable
Severity: critical → S3
You need to log in before you can comment on or make changes to this bug.