Graphics driver crash
Reported by
aralya...@gmail.com,
May 27 2016
|
|||||
Issue description
Chrome Version : 51.0.2704.63 (32-Bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:Not tested
Firefox:FAIL 49.0a1 already reported as bug see (https://bugzilla.mozilla.org/show_bug.cgi?id=1246146)
IE:Fail
What steps will reproduce the problem?
(1)Open crashGraphicsDriver.html
(2)Windows shows a message in the right corner (driver crash)
(3)
What is the expected result?
No graphics driver crash
What happens instead?
crash of the graphics driver
Please provide any additional information below. Attach a screenshot if
possible.
I'm not sure if this is the right place for this kind of bugs...
The reason for the crash is a big integer value in the webgl function
gl.drawArrays(3, 0, 2147483646);
Windows 8.1
Intel(R) HD Graphics Family 10.18.14.4264
,
Apr 10 2017
This sample caused Chrome to be irresponsive on my Mac laptop. Since there is no buffer bound at all, I thought we should reject gl.drawArrays() with a GL error, but apparently there is a bug somewhere.
,
Apr 14 2017
zmo, since you've looked into this some, are you able to fix this or assign to somebody else who can?
,
Apr 17 2017
Per offline discussion with kbr, such case (calling drawArrays with huge count without a buffer source) is not considered a security threat and therefore allowed. So now the only question: is the crash originally reported on Windows Intel driver truly a crash in the driver, or it's actually Chrome GPU process watchdog kicks in and kills GPU process because the drawArrays call took too long. aralyaman@gmail.com: can you run the html on the affected machine, and attach the about:gpu content here?
,
Jun 20 2017
,
Nov 10 2017
WontFix without any feedback from original reporter :( |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cbiesin...@chromium.org
, Jul 19 2016