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

Issue 666249 link

Starred by 3 users
Status: Duplicate
Merged: issue 666984
Owner:
alph@chromium.org
Closed: Nov 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
l...@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Tab crash is seen in chrome:/lhistory page on recording 'Record Allocation Timeline' profile in Dev tools

Project Member Reported by mmanchala@chromium.org, Nov 17 2016 
Version: 56.0.2923.0
OS: Ubuntu 14.04,Windows

What steps will reproduce the problem?
(1)Launch Chrome -> Go to chrome://history page and press F12 to open Dev tools
(2)Now Go to Profiles Section -> Select 'Record Allocation Timeline' profile option-> Now Click on Start Button 
(3)Click on 'Stop Recording heap profile' icon and observe Tab Crash  (Please refer video)


Expected: Tab crash should not be seen in chrome://history page on recording 'Record Allocation Timeline' profile
Actual: Instead Tab Crash is seen 

Below is the Crash Id:
Crash ID Chrome (Server ID: dae466af00000000)


This is Regression Issue broken in M-56
will provide Bisect info soon
Actual_TabCrash.ogv
1.2 MB View Download
Expected.ogv
1.4 MB View Download

Comment 1 by mmanchala@chromium.org, Nov 17 2016

Labels: hasbisect-per-revision OS-Chrome OS-Mac OS-Windows
Owner: l...@chromium.org
Status: Assigned (was: Untriaged)
Note:
1.Issue is also seen on Mac and Chrome OS 
2.issue is see on Chrome://md-settings page also

Manual good and Bad Builds:
Good Build: 56.0.2915.0
Bad Build:  56.0.2916.0

CHANGELOG URL::
https://chromium.googlesource.com/chromium/src/+log/b4f93809bffea47ad24b08988328dcf5c0cfa8b4..148b74d5ebd0792c3c6b000a2e7619637078a1eb

Suspecting https://codereview.chromium.org/2486953002 from Changelog

@luoe :  Please feel free to re-assign if its not related to your change

Comment 2 by l...@chromium.org, Nov 17 2016

Cc: l...@chromium.org
Owner: alph@chromium.org
@alph, could you please take a look?  The bisect pointed to my change that broke compile-frontend, but it's not related to my changes.

Comment 3 by alph@chromium.org, Nov 23 2016

Mergedinto: 666984
Status: Duplicate (was: Assigned)
►

Sign in to add a comment