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

Issue 734026 link

Starred by 1 user
Status: Duplicate
Merged: issue 733181
Owner:
tebbi@chromium.org
Closed: Jun 2017
Cc:
█ abdulsyed@chromium.org
█ amineer@chromium.org
pbomm...@chromium.org
adamk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Consistent crashing with websites using drawing/svg/css features

Reported by filippo....@geopal-solutions.com, Jun 16 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36

Steps to reproduce the problem:
1. Make sure you have Hardware Acceleration turned on
2. Goto this link http://examples.sencha.com/extjs/5.1.0/examples/kitchensink/?charts=true#pie-basic
3. Keep moving your mouse from one slice to the other of the pie chart

What is the expected behavior?
It should just keep working

What went wrong?
Chrome gives the "Aw Snap" screen after moving from one slice to the other of ExtJS charts (5.1.0).

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 59.0.3071.104  Channel: stable
OS Version: OS X 10.12.5
Flash Version: 

Happens only when Hardware Acceleration is turned on.
This is not isolated to Sencha's kitchen sink and extends to our product. We temporarily worked around it by disabling some visual features in our product, but doing so charts are not as nice.

Comment 1 by pbomm...@chromium.org, Jun 16 2017

Cc: pbomm...@chromium.org abdulsyed@chromium.org adamk@chromium.org amineer@chromium.org
Components: Blink>JavaScript
Labels: -Type-Bug ReleaseBlock-Stable M-60 M-61 M-59 OS-Android OS-Chrome Type-Bug-Regression
Status: Available (was: Unconfirmed)
Able to reproduce the issue with latest Chrome stable i.e., 59.0.3071.104 on Windows, Mac and Linux and this is regression which started in M59, Works fine in M58. 


Please find the bisect range below :
You are probably looking for a change made after 455719 (known good), but no lat
er than 455720 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/772559ed7f79de8395dfb24eae582172a1840655..5e921f820bc0a86566e25b279019ba965535230e




Note : Able to reproduce the issue in M61 and 60 as well, Any fix should be merged in these channels as well. This should be crashing on Android and ChromeOS

Comment 2 by pbomm...@chromium.org, Jun 16 2017

Labels: -Pri-2 Pri-1

Comment 3 by pbomm...@chromium.org, Jun 16 2017

Owner: tebbi@chromium.org
Status: Assigned (was: Available)
Assigning to tebbi based in  issue#733181

Comment 4 by adamk@chromium.org, Jun 16 2017

Labels: OS-Linux OS-Windows

Comment 5 by adamk@chromium.org, Jun 16 2017

Labels: Merge-Request-60 Merge-Request-59
Mergedinto: 733181
Status: Duplicate (was: Assigned)
Confirmed that this is  issue 733181 , and that it's fixed by tebbi's a969ab67f8e1e7475d9b26468225c3a772890c64. That commit is another very safe merge, for what it's worth.
Project Member

Comment 6 by sheriffbot@chromium.org, Jun 16 2017

Labels: -Merge-Request-60 Hotlist-Merge-Review Merge-Review-60
This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by adamk@chromium.org, Jun 16 2017

Labels: -Merge-Request-59 -Merge-Review-60
Removed merge requests, will handle merge over in  issue 733181 .
►

Sign in to add a comment