Issue metadata
Sign in to add a comment
|
WebGL content repeatedly "hits a snag" when browser is minimized and restored
Reported by
kingofst...@gmail.com,
Oct 20 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Example URL: http://www.pro32.ap.org/article/waiting-game-browns-jackson-close-choosing-starting-qb Steps to reproduce the problem: 1. Open up more than one tab, each running some WebGL content. 2. Minimize the browser 3. Restore the browser What is the expected behavior? The page responds normally and the WebGL content does not crash. What went wrong? WebGL crashes and Chrome displays "Rats! WebGL hit a snag." The WebGL content disappears. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes version 0.61 Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 27.0 r0 We have dozens of WebGL-based games and apps that have worked perfectly on all previous versions. This problem is introduced in version 0.62.
,
Oct 20 2017
Hi, This issue seems to be related to: https://bugs.chromium.org/p/chromium/issues/detail?id=773199 Could you check chrome://gpu page after minimizing & maximizing Chrome?
,
Oct 21 2017
Confirmed on a Windows 10 workstation that this is the same problem as Issue 773199 : [9776:6988:1020/170415.328:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000002A86F43B4F0]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface [9776:6988:1020/170415.328:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed. [9776:6988:1020/170415.328:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM [9776:6988:1020/170415.328:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems. GpuProcessHostUIShim: The GPU process exited normally. Everything is okay. Duplicating into the other bug, but this indicates the problem's more serious, and easily reproducible, than originally thought. I can reproduce it every time by restarting the browser, opening a new window, navigating to this bug, control-clicking the AP link above, switching to that tab, and minimizing the window. It's not just happening with a fresh user profile.
,
Oct 21 2017
Hi Ken, In that Issue report I just intend to provide a way to always reproduce this issue. Actually this issue can be observed on many platforms without clearing user profile, but it may not be reproduced every time. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Oct 20 2017Labels: -Type-Bug M-62 Needs-Triage-M62 Needs-Bisect Type-Bug-Regression