WebGL functionality stops after demo causes lockup
Reported by
scottt...@gmail.com,
Jun 21 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10575.55.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Example URL: https://demo.marpi.pl/dark_haze/ Steps to reproduce the problem: 1. Attempt to run this demo. 2. 3. What is the expected behavior? The demo should run What went wrong? Chrome desktop becomes unresponsive including all other apps like the COG - System Info Viewer. At that point the Chromebook screen will go black as though the OS went through some kind of reset. The desktop then returns however from that point on all web content requiring WebGL will show a white box at the top of the screen that says... "Your graphics card does not seem to support WebGL Find out how to get it here" WebGL functionality does not return until the system is rebooted. I have never seen a Chrome OS reset like this or loss of WebGL for any other site. This site is not important. The fact that it breaks Chrome OS is quite surprising though. It would seem this is worth looking into. This is repeatable. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: 10575.55.0 Flash Version:
,
Jun 23 2018
I should note I have never seen what appears to be a hard crash like this in all my time using Chromebooks which has been a number of years now. Again, the demo is unimportant, but the full crash - desktop reset is certainly interesting so I thought the dev team would want to know about it.
,
Jun 23 2018
The Samsung Chromebook 2 was tested with... Version 66.0.3359.158 (Official Build) (32-bit)
,
Jun 23 2018
Samsung continues to run demo correctly with OS updated to... Version 67.0.3396.87 (Official Build) (32-bit)
,
Jun 25 2018
,
Jun 25 2018
Something about the shaders this demo is using or the draw calls it's making is almost certainly tripping over a corner case in Intel's graphics driver for ChromeOS. It might be common to the Linux platform too (I don't have a machine to test with) but it's definitely working on a MacBook Air with Intel HD 6000 GPU running 10.12.6 (sorry for not testing with a more recent OS version but it's a proof point that it's not a hardware problem.) Also, please also copy/paste (plaintext is fine) the contents of about:gpu when filing any graphics bug against Chrome. We need it in order to know the exact GPU type to be able to test and triage on similar hardware.
,
Jun 25 2018
Also: if the demo is causing a GPU hang and reset on ChromeOS then Chrome is responding as intended by forbidding WebGL until Chrome (or, in this case, the machine) is restarted. From that standpoint Chrome's graphics infrastructure is working as intended.
,
Jun 25 2018
I tried on eve, and there was no problem running the demo. I then tried on link and I do see the GPU watchdog kick in, but it's not because of a GPU hang; instead I suspect the shader takes too long to compile...
,
Jun 25 2018
Thanks marcheu@ for triaging. Since it sounds like this is working on recent hardware (how old is link? 4 years?) and Chrome's response is correct I'm closing this as WontFix. However note that we will finally add background shader compilation support to WebGL in Issue 849576 so that if applications are restructured to use it (really a one-line change) then they will be able to take as long as they want to compile their shaders. |
||||
►
Sign in to add a comment |
||||
Comment 1 by scottt...@gmail.com
, Jun 23 2018