New issue
Advanced search Search tips

Issue 658123 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 581997
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Trying to run WebGL in a Chrome Extension in development- "Aw, Snap!" when attempting to render WebGL

Reported by straube....@gmail.com, Oct 21 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
X-Posting from my comment on GitHub (https://github.com/anvaka/VivaGraphJS/issues/184)
1. Download files into a single directory from gist here: 
https://gist.github.com/adamstraube/251fbaa929c3ec299240d2cd4feaa965
2. Go to chrome://extensions/, click Load unpacked extension and point it to the directory with the files above
3. Goto www.google.com 

(if you are redirected to regional Google URL then change the "matches" line in the manifest.json file to the regional Google URL)

Commenting out "graphics : graphics" line stops the crash

What is the expected behavior?
Runtime JS: https://anvaka.github.io/VivaGraphJS/demos/other/webglInput.html

Code: https://github.com/anvaka/VivaGraphJS/blob/master/demos/other/webglInput.html

What went wrong?
The Chrome browser crashes ("Aw, Snap!"). I am unable to get any further info out of this issue as the Developer tools stop responding when this happens.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 

Comment 1 by e...@chromium.org, Oct 21 2016

Components: -Blink Platform>Extensions Blink>WebGL

Comment 2 by kbr@chromium.org, Oct 21 2016

Mergedinto: 581997
Status: Duplicate (was: Unconfirmed)
Please re-test with Dev Channel. This should be fixed there.

Updating to Chrome Version 54.0.2840.71 stops this issue from occurring. This fix has been pushed into the regular version of Chrome.

Comment 4 by kbr@chromium.org, Oct 26 2016

Glad it's working on Stable now.

Sign in to add a comment