Issue metadata
Sign in to add a comment
|
Two Crash ID's generated for intentional browser crash |
||||||||||||||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (Linux) What steps will reproduce the problem? (1) Launch chrome (2) navigate to "about://inducebrowsercrashforrealz" this will close the chrome browser. (3) Relaunch chrome and navigate to chrome://crashes What is the expected result? Only Single crash ID is generated. What happens instead? Two crash ID's are generated Bisect Info: ============= Good Build : 58.0.3019.0 Bad Build : 58.0.3020.0 The Change Log: https://chromium.googlesource.com/chromium/src/+log/58.0.3019.0..58.0.3020.0?pretty=fuller&n=10000 Unable to provide the per-revision result because invoked chrome builds are not generating crash id's even appending --times=2 argument The manual suspect CL : Review-Url: https://codereview.chromium.org/2711513003 rdevlin.cronin@ - Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner. Note: Issue is not observed on Mac OS & Windows
,
Aug 30 2017
rdevlin.cronin@ these are the two crash id's that generated for about://inducebrowsercrashforrealz 69da1248d21a9f1f : https://crash.corp.google.com/browse?stbtiq=69da1248d21a9f1f de856e91134c9d04 : https://crash.corp.google.com/browse?stbtiq=de856e91134c9d04 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rdevlin....@chromium.org
, Aug 25 2017