Regression: Tab crash is seen on adding breakpoints in devtools |
||||||||||
Issue descriptionVersion: 56.0.2918.0 dev OS: Ubuntu 14.04,Windows What steps will reproduce the problem? (1)Launch chrome and open devtools on any page >> Go to profiles tab and record record "Javascript CPU profile" (2)Now click on links of recorded data so that file opens in sources tab[Please refer video] (3)Now try to add breakpoints by clicking on empty space above scale Expected: No crash should be seen on adding breakpoints. Actual:Instead tab crash is seen. This is a regression issue. Will provide bisect info soon. Crash id: 2b9dcfcf00000000 , 525d4fcf00000000
,
Nov 14 2016
Issue is reproducible on the latest canary(56.0.2918.0) on Mac OS 10.11.6 as well.
,
Nov 14 2016
Using the per-revision bisect providing the bisect results, Good build:56.0.2915.0 (Revision:431137) Bad build:56.0.2916.0 (Revision:431463) You are probably looking for a change made after 431409 (known good), but no later than 431410 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/6e7cdc64930f4073c068b56eeae5625cc038756e..b64455d31709242af63083dc626b6959c21510b5 Possible Suspect URL: https://chromium.googlesource.com/v8/v8/+/f56685d0640db162a3509c6576987f88945c963f rom the CL above, assigning the issue to the concern owner @yangguo - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Review-Url: https://codereview.chromium.org/2481363009 Thanks !
,
Nov 14 2016
,
Nov 14 2016
That CL reverted a fix landed just a few hours prior, so I doubt it can cause any issues. The original fix has been relanded though. So let's wait and see.
,
Nov 18 2016
Issue got fixed and is not seen in 56.0.2924.0 dev. Hence adding TE-Verified labels.
,
Nov 30 2016
yangguo@: Could you please close the issue if the CL has been relanded and no further work to be done here.
,
Dec 7 2016
yangguo@: Friendly reminder, Could you please update on comment #7. Thank you!
,
Dec 7 2016
,
Dec 7 2016
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.
,
Dec 7 2016
No merge necessary. The fix is included in M56.
,
Dec 16 2016
This bug requires manual review: No test file found in commits. Please contact the milestone owner if you have questions. Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 16 2016
This bug requires manual review: No test file found in commits. Please contact the milestone owner if you have questions. Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 16 2016
[Automated comment] removing mislabelled Merge-Review-56, Hotlist-Merge-Review |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by sc00335...@techmahindra.com
, Nov 14 2016