1342666 - WebGL2: browser crash on macOS 10.12.4 Beta

Status: RESOLVED WORKSFORME

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

Description

[Andre Weissflog]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3023.0 Safari/537.36

Steps to reproduce:

Any Firefox version
OS: macOS 10.12.4 Beta (16E163f)
MacBook Pro (Retina, 13-inch, Mid 2014)
Intel Iris 1536 MB

What steps will reproduce the problem?
(1) if necessary, enable WebGL2 and go here: https://floooh.github.io/oryol-webgl2/asmjs/MultipleRenderTarget.html
(2) FF will hang or crash
(3) try the same on Windows, the demo works fine

The problem seems to happen down in the macOS OpenGL driver, since the problem also happens when running the same demo as native code.

Related Chrome ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=696187

Comment 1

[Michael Leu[:Lenzak](UTC+8)]

I can reproduce it with Firefox Release on a late-2013 Macbook pro 15-inch with Mac OSX 10.11.6

And this website runs fine if it utilizes discrete GFX (NVidia GT750M in this case).

I think it is caused by buggy Intel GFX driver.

Comment 2

[Andre Weissflog]

Attachment: minimal reproduction test

The attached zip contains a human-readable minimal repro (an index.html and JS file). Opening the index.html in FF (or Chrome) on the right Mac/OSX config will freeze the window system for 10..20 seconds, and eventually the browser needs to be killed with Force Quit.

Comment 3

[Milan Sreckovic [:milan] (needinfo for best results)]

Andre, did you also file a bug with Apple?  Given that this fails in native code, that's probably the first place to start with.

Comment 4

[Andre Weissflog]

Nope, but AFAIK the Chrome team did and I think/hope they have a direct contact at Apple they can nag if things don't move fast enough. I basically gave up on Radar, never ever heard a peep out of it when writing bugs there ;)

Comment 5

[Andre Weissflog]

Btw: I can no longer reproduce this issue (I'm on the 10.13 Beta now). Unfortunately I cannot check the state of the 10.12 release version.

Comment 6

[Timothy Nikkel (:tnikkel)]

Sounds like this was a bug on Apple's side that they have fixed. The linked chromium issue says that Apple fixed the bug, and reporter here says the bug is fixed. Closing.