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

Issue 777735 link

Starred by 3 users
Status: Duplicate
Merged: issue 773199
Owner: ----
Closed: Oct 2017
Cc:
█ abdulsyed@chromium.org
█ kbr@chromium.org
gov...@chromium.org
█ manoranj...@chromium.org
chrome-conops-escalation@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Feedback Prestable] Spike in WebGL not working issue

Project Member Reported by jainabhi...@chromium.org, Oct 24 2017 
Chrome Version: 62.0.3202.62
OS: Windows 

What steps will reproduce the problem?
1. Open https://get.webgl.org/
2. Minimize the window
3. Reopen it (the cube disappears).
4. Reload the page (F5)
5. Bingo. The error "Rats! WebGL hit a snag" appears.

This problem also happens on Facebook.com, having an open chat window and minimizing the Google Chrome window and then opening it.

The most mysterious thing is that in incognito mode this problem does not occur.

** Another unique comment in user feedback **
When I try to run unpacked extensions, I write: WebGl is not supported. On the old version, everything was fine. In chrome: // gpu prints this:
WebGL: Hardware accelerated and at reduced performance
WebGL2: Unavailable
In chrome: // flag - WebGl is enabled


In almost all the reports users have kmendfapggjehodndflmmgagdbamhnfd : CryptoTokenExtension : version 0_9_46 extension installed.

This extension is not available in Chrome web store.


More reports and feedback trends can be found using http://pulse/#feedbackneutron?base_params=14rdf9wh
0.jpeg
60.6 KB View Download

Comment 1 by jiawei.s...@intel.com, Oct 24 2017

Cc: kbr@chromium.org
Hi,

This issue seems to be the similar one as:
https://bugs.chromium.org/p/chromium/issues/detail?id=773199

Could you verify if there are any error messages in chrome://gpu page?

Comment 2 by jainabhi...@chromium.org, Oct 25 2017 

We dont have GPU details in user feedback.
However, all of these reports have CryptoTokenExtension extension installed.

Comment 3 by dtapu...@chromium.org, Oct 25 2017

Components: Blink>WebGL

Comment 4 by kainino@chromium.org, Oct 25 2017

Labels: Needs-Feedback
The CryptoTokenExtension (kmendfapggjehodndflmmgagdbamhnfd) is bundled with all versions of Chrome and Chromium. _All_ Chrome users should have it.

> WebGL: Hardware accelerated and at reduced performance
This is what we expect to see after 3 "WebGL hit a snag" errors which were caused by GPU process crashes.

I can't quite tell if this issue was there in M61 as well, but it does seem to have spiked in M62.

jainabhishek: It sounds like you were able to reproduce the problem. If so, please reproduce it and then copy+paste the full contents of chrome://gpu into a comment here.

Meanwhile I'll quickly try to repro on my Windows/AMD machine but I don't think it's likely to repro.

Comment 5 by kainino@chromium.org, Oct 25 2017

Labels: -Needs-Feedback
Wow, I was actually able to repro on the first try on both Windows/AMD and Windows/Intel. This is a pretty serious issue.

[13092:8732:1025/120010.493:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-0000026826BCBF20]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[13092:8732:1025/120010.493:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[13092:8732:1025/120010.493:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[13092:8732:1025/120010.493:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.

jainabhishek: your chrome://gpu is no longer needed.

Comment 6 by kainino@chromium.org, Oct 25 2017

Components: Internals>GPU
Seems more likely this is general GPU rather than WebGL, not sure though.

Comment 7 by kainino@chromium.org, Oct 25 2017

Owner: kainino@chromium.org
Status: Started (was: Untriaged)
Bisecting.

Comment 8 by kainino@chromium.org, Oct 25 2017

Mergedinto: 773199
Owner: ----
Status: Duplicate (was: Started)
Never mind, spoke with my teammates at lunch and realized that this is in fact the same as  issue 773199 , as pointed out by jiawei.shao.
►

Sign in to add a comment