New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 741062 link

Starred by 1 user
Status: WontFix
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Jul 2017
Cc:
█ kbr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Observing WebGl crashes when tried to launch "Walking Down the L trian" WebGl experiment.

Project Member Reported by pbomm...@chromium.org, Jul 11 2017 
Chrome Version: 59.0.3071.115
OS: Win7
GPU : ANGLE (NVIDIA Quadro FX 580 Direct3D11 vs_4_0 ps_4_0) - Details of GPU are attached

What steps will reproduce the problem?
(1) Install and launch Chrome
(2) Visit "http://itp.fengyizhu.com/WalkingDowntheLTrain/"

What is the expected result?
WebGl experiment should be launched

What happens instead?
Observing "Rats! WebGL hit a snag"
Also observed that whole Chrome browser's turned black and system tray displayed "Display driver stopped responding and has recovered" please find below screenshot.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


Note : Will check and update the behavior on Beta and Dev(Since when I hit this snag I was loosing the bug details which enter will update them soon)
gpu.htm
52.5 KB View Download
webgl1.png
28.1 KB View Download

Comment 1 by pbomm...@chromium.org, Jul 11 2017

Labels: Needs-Bisect
observed similar behavior on Chrome beta(60.0.3112.50), Dev(61.0.3153.0) and canary(61.0.3154.0).

Note : Didn't see this behavior on Windows 10 and Mac both had different GPU cards not the one similar to the Win7 machine where I saw this issue.

Comment 2 by kbr@chromium.org, Jul 11 2017

Owner: kbr@chromium.org
Status: WontFix (was: Available)
Chrome's behaving as expected when running a WebGL page that stresses the graphics card too much and causes a Timeout Detection and Recovery event on Windows. It runs fine on my Windows 10 workstation with AMD R7 240 GPU.

If you reduce the app to something manageable (it's huge, I checked the sources) and it seems there's no excuse for it TDRing then please either reopen this bug with the test case, or file a new bug and assign it to me.

Closing as WontFix - working as intended.
►

Sign in to add a comment