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

Issue 590504 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
nyerramilli@chromium.org
█ ranjitkan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Rats! WebGL hit a snag.

Project Member Reported by dbloch@google.com, Feb 28 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.0 Safari/537.36

Steps to reproduce the problem:
See below.

What is the expected behavior?

What went wrong?
No repro steps per se.  I've seen an error bar saying "Rats! WebGL hit a snag" twice in the two hours since upgrading to 50.0.2661.0.  Once from Google Maps, once from the New York Times.

Did this work before? Yes Two hours ago on previous canary release.

Chrome version: 50.0.2661.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by nyerramilli@chromium.org, Feb 29 2016

Cc: nyerramilli@chromium.org
Labels: Needs-Feedback
Thanks for the report.

Tested the issue on Win7, Chrome Canary #51.0.2663.0, navigated to New York Times & Google maps - did not observe any crash.

Could you please check with the latest Chrome canary and let us know if the issue still persists also please provide crash id from chrome://crashes.

Comment 2 by dbloch@google.com, Feb 29 2016 

I haven't seen it since those two times.

They didn't produce crash dumps when they happened.

Comment 3 by ranjitkan@chromium.org, Mar 29 2016

Cc: ranjitkan@chromium.org
Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Thanks for the update, closing the issue as per above comment. Please reopen or raise a new issue if it reappears.
►

Sign in to add a comment