Chrome crash when running the JetStream 1.1 benchmark.
Reported by
canx....@intel.com,
Nov 8
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Running the JetStream: https://browserbench.org/JetStream/ 2. Click the "Start Test" What is the expected behavior? All of the benchmark should get result ASAP. What went wrong? The "cdjs" of benchmark always get "Running" status.Click reload the page button Chrome crash:"Aw, Snap!" Did this work before? Yes 71.0.3578.0 Chrome version: 72.0.3604.0 Channel: canary OS Version: 10.0 Flash Version: I found the r604896 is root cause by the bisect-build.py. r604894 good/r604897 bad.
,
Nov 8
,
Nov 8
,
Nov 9
Able to reproduce the issue on reported version# 72.0.3604.0 using Mac 10.14.0, Ubuntu 14.04 and Windows-10, hence providing Bisect Info Bisect Info: ================ Good build: 72.0.3599.0 Bad build: 72.0.3600.0 You are probably looking for a change made after 604895 (known good), but no later than 604896 (first known bad). https://chromium.googlesource.com/chromium/src/+log/6b8d6ee9cb0e7ecd678ad9102702b9ebc593f502..710b03cd5742af660d5f87da9580777e494e9c84 Unable to find the correct suspect from above change log, hence marking this issue as Untriaged and requesting someone from the Dev team help in assigning it to correct owner. Adding ReleaseBlock-Stable for M-72, feel free to remove it if is not applicable. Thanks!
,
Nov 13
Friendly ping to get an update as it is marked as RBS. Thanks..!
,
Nov 15
Is this a duplicate of Issue 904546 ? Unfortunately there's no stack trace.
,
Nov 15
In the range https://chromium.googlesource.com/v8/v8/+/b8a911314d00e5c866399b58533a79bddce45fb6 looks interesting. Benedikt, PTAL.
,
Nov 16
According to the Comment 6, and I verified this issue on Chrome Canary 72.0.3611.0. This issue has been fixed. Thanks.
,
Nov 19
Closing according to comment #8. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by yang...@intel.com
, Nov 8