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

Issue 596127 link

Starred by 2 users
Status: Duplicate
Merged: issue 581997
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Sep 2016
Cc:
█ kavvaru@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Bug

Blocked on:
issue 485634


Sign in to add a comment

THREE.WebGlRenderer() breaks extensions.

Reported by minshal...@gmail.com, Mar 18 2016 
Chrome Version       : 49.0.2623.87 (Official Build) (64-bit)


What steps will reproduce the problem?
(1) Grab and load the extension located here: https://github.com/minshallj/broken_extension
(2) Point your browser to www.foo.com (just because that's the url the extension is active on)
(3) Watch as things break

What is the expected result?

The page should load.


What happens instead?

Right when the THREE.WebGlRenderer() call is executed, the browser crashes. This did not happen on chrome versions less than 48.


Please provide any additional information below. Attach a screenshot if
possible.

It might be worth noting that the call doesn't break a webpage that uses it, just an extension.

Comment 1 by kavvaru@chromium.org, Mar 21 2016

Cc: kavvaru@chromium.org
Components: Platform>Extensions Blink>WebGL
Labels: M-51 hasbisect OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.3 using chrome version 49.0.2623.87.But it is working fine on Canary 51.0.2686.0
Please find the reverse bisect information as below

Narrow Bisect::
Good::51.0.2673.0   -- (official build 380313)
Bad::51.0.2672.0   --- (official build 380022)

CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/c18f9cc14a916cf131b6cb8f001e469d0a26de43..3754aa680c145bbf5211b7604406ebf2d7d627e2

blink CL :
https://chromium.googlesource.com/skia.git/+log/042f859c19f7..8a21c9fe7f5f

Unable to find the exact CL from the above CL.Hence marking it as Untriaged.

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

Blockedon: 485634
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)
I'm pretty sure this was caused by the fix for  Issue 485634  and is a duplicate of  Issue 581997 . I'll try to get to the bottom of this.

Comment 3 by minshal...@gmail.com, Sep 6 2016 

This looks to be broken again in `Google Chrome 53.0.2785.92` and `Google Chrome 52.0.2743.116`. It was however working fine in 51 for me.

Comment 4 by kbr@chromium.org, Sep 7 2016

Mergedinto: 581997
Status: Duplicate (was: Assigned)
I'm 99% sure this is a duplicate of  Issue 581997  for which a fix just landed. Sorry for the breakage, but this will be fixed in Chrome 55.
►

Sign in to add a comment