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

Issue 753417 link

Starred by 1 user
Status: Duplicate
Merged: issue 575305
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Aug 2017
Cc:
█ kbr@chromium.org
geoffl...@chromium.org
bsep@chromium.org
█ hubbe@chromium.org
pkasting@chromium.org
zmo@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 737570


Sign in to add a comment

Weird styled infobar: "Rats! WebGL hit a snag" on keep.google.com

Project Member Reported by rpop@chromium.org, Aug 8 2017 
Chrome Version: 59.0.3071.115
OS: Win10

What steps will reproduce the problem?
(1) go to keep.google.com

What is the expected result?
No infobar, or infobar that conforms to Chrome style (white, no carrot, smaller height)

What happens instead?
Odd infobar. See attached. Strings should also be reviewed.

Not sure if this is actually Chrome or from webGL?
gpu.htm
127 KB View Download
webgl.PNG
24.5 KB View Download

Comment 1 by kbr@chromium.org, Aug 8 2017

Owner: kbr@chromium.org
Status: Assigned (was: Available)
Please provide about:gpu from your system.

We are going to remove this infobar in  Issue 575305 , regardless, but let's figure out why it's showing up often on your machine. The text dates back many years.

(Keep uses WebGL for their drawing functionality and they load it unconditionally and eagerly -- see b/33350182 ).

Comment 2 by kainino@google.com, Aug 8 2017

Blockedon: 737570
Labels: Needs-Feedback
Possible duplicate of issue 737570

Comment 3 by rpop@chromium.org, Aug 8 2017 

@1 this is attached to the initial report as gpu.htm

Comment 4 by kbr@chromium.org, Aug 8 2017

Cc: hubbe@chromium.org geoffl...@chromium.org
Ah, sorry, didn't see the about:gpu earlier, was looking for its contents.

Hmm. Intel integrated GPU, lots of errors including a video-related error, and a GPU process crash. If you click "Reload" on the infobar, or restart Chrome, does the problem persist? I'd expect it to go away and not repeat very often.

Comment 5 by rpop@chromium.org, Aug 8 2017 

Reloading via infobar does make it go away. Earlier today, visiting keep in a new tab repro'd it reliably, but it doesn't anymore.

My main concern was the UX shown in this scenario. Glad to hear improvement is on the way.

Comment 6 by kainino@google.com, Aug 8 2017

Labels: -Needs-Feedback

Comment 7 by kbr@chromium.org, Aug 8 2017

Mergedinto: 575305
Status: Duplicate (was: Assigned)
OK, thanks for confirming. The UX will improve as soon as the old navigation code is removed and we can reliably get the signal that the user initiated a navigation. Let me duplicate this into  Issue 575305 .
►

Sign in to add a comment