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

Issue 608897 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

WebGL crashes during shader compilation on certain Chromebooks

Reported by eno...@onshape.com, May 3 2016

Issue description

Chrome Version: 50.0.2661.91 beta
Chrome OS Version: Platform 7978.66.0 (Official Build) beta-channel peach_pit
Chrome OS Platform: Samsung Exynos5
Network info: Issue does not depend on network

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Navigate to https://cad.onshape.com/documents/a8e844bbd4db824888d97cce/w/ac5392152c36441ce0a1e2b3/e/5aad4c1ace9779c99d5f0f27
(2) Observe that WebGL crashes

Expected Result:
On most systems (other Chromebooks included) the page loads without issue.

Actual Result:
On a certain class of Chromebook the page will cause a crash.  Samsung models seem to be affected, as does the Asus Chromebit.

How frequently does this problem reproduce?
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
Users cannot use any page on our site that uses WebGL.

Please provide any additional information below. Attach a screen shot or
log if possible.
The earliest report of this problem was April 13.  Prior to that the same platform had worked without issue.

The issue has been tracked down to the compilation of a specific shader in our system.  When that shader is altered, the crash is no longer triggered.  We have a pending work-around, however it has not reached production yet and hence the problem is still reproducible.  If there is an underlying platform issue, it would be good to see that cause fixed.
 
Components: Blink>WebGL

Comment 2 by kbr@chromium.org, May 13 2016

Cc: marc...@chromium.org
Stephane, do you have a machine on which you can reproduce this?

Cc: -marc...@chromium.org arm@chromium.org
Owner: marc...@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: dbehr@chromium.org ihf@chromium.org h...@chromium.org

Comment 5 by h...@chromium.org, May 13 2016

Reproduced on peach_pit 50.0.2633.0 / 7867.0.0 dev channel
Still reproduced on peach_pit 51.0.2704.42 / 8172.28.0 dev channel

Comment 6 by ihf@chromium.org, May 13 2016

The M50 and earlier crashes on that url show a mali tcmalloc corruption, but the backtrace is bad:
https://crash.corp.google.com/browse?stbtiq=cb3b220a00000000

Newer crashes indicate a shader problem, but the backtrace is still pretty bad
https://crash.corp.google.com/browse?stbtiq=c9a151ec00000000


Having flicker issue on some websites starting June 16, 2016 on ASUS C100P. Consistent on website www.freep.com , sometimes reports "Rats WebGL hit a snag" and "Dear monitor its not working out between us"

Did a Powerwash, problem persists.

Chrome Build: 51.0.2704.79 (Official Build) (32-bit)

Comment 8 by ihf@chromium.org, Jun 17 2016

John, a fix for your issue (which is a Chromebook Flip/veyron and fixed by disabling FBC) is going out in the next few days on the stable channel. Sorry about that!

Comment 9 by lmcart...@gmail.com, Jun 18 2016

Adding CBC discussion possibly describing this issue on a Veyron_Speedy (Asus C201) on Stable51.0.2704.79

#CBC-RS/TC-watchlist
Status: Fixed (was: Assigned)
Yes the fix should roll out soon.
Labels: VerifyIn-53
Labels: VerifyIn-54
Labels: VerifyIn-55

Comment 15 by dchan@google.com, Nov 19 2016

Labels: VerifyIn-56

Comment 16 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 17 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 18 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59
I keep on getting "Rats WebGL hit a snap while entering a graphic game called pattermore in www.pottermore.com/patronus . Please help me 
Screenshot 2017-05-11 at 8.53.54 PM.png
6.9 KB View Download
This issue is already closed; please file a new bug report. When you do so,
include your GPU info by copy+pasting the chrome://gpu page into the bug
description. Thanks!
Status: Verified (was: Fixed)
Verified on 9460.34.0/59.0.3071.41 and 9557.0.0/60.0.3101.0

Sign in to add a comment