Issue metadata
Sign in to add a comment
|
Regression: On Crashing a browser incorrect date for Crash ID is seen in "chrome://flash"
Reported by
lpa...@etouch.net,
Jan 11 2017
|
||||||||||||||||||||
Issue descriptionChrome: 56.0.2924.59 (Official Build) 8f17c5e623e7acc34e976fe9b76ff7b6025ba26c-refs/branch-heads/2924@{#725} (32/64 bit) OS: Windows(7,8,8.1,10) 1. Launch chrome ,go to NTP and navigate to 'chrome://crash' to crash NTP. 2. Then Crash Browser using "about:inducebrowsercrashforrealz"(Browser crashes) ,Open Borwser. 2. Navigate to chrome://flash" and observe under crash id. Actual Result: Incorrect date is displayed for Crash ID in chrome://flash. Expected Result: Current Date should be displayed. This is regression issue broken in 'M 55' and will soon update the bisect info: Manual bisect info: Good Build No: 55.0.2858.0 Bad Build No: 55.0.2859.0 Note:1.Above issue is not seen on Mac and Linux OS. 2.Above issue is not seen in chrome://crashes that is current date is displayed.
,
Jan 12 2017
With respect to comment 1: ChangeLog info: https://chromium.googlesource.com/chromium/src/+log/55.0.2858.0..55.0.2859.0?pretty=fuller&n=10000 Suspecting: r418063 ? Note: Unable to narrow down the range using tool bisect as crash id is not generated in chromium builds. @scottmg: Please help me to reassign this issue if your change is not cause for it.
,
Jan 18 2017
able to reproduce the issue on win10 chrome version 57.0.2985.0 scottmg@, could you please take a look
,
Jan 24 2017
Able to reproduce the issue on windows 7 using chrome version 58.0.2990.0. scottmg@ Please look into this issue. Thanks, |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Jan 11 2017Status: Untriaged (was: Unconfirmed)