Kernel crash does not show on chrome://crashes page if log files have been corrupted |
|||||||||
Issue descriptionChrome Version: 57.0.2987.54 beta Platform 9202.28.0 (Official Build) beta-channel squawks Firmware Google_Squawks.5216.152.76 What steps will reproduce the problem? 1. Sign in to the device. 2. Open new tab and navigate to "about:crash". ( To trigger render crash) 3. Open new tab and navigate to "about:inducebrowsercrashforrealz" ( To trigger browser crash) 4. Press key combination of alt + F10 + xxx ( to generate Xorg and Kernel crashes ) 5. Open about:crashes and click on "Start Uploading Crashes" link to upload the crash report What is the expected result? All crashes (browser, render & kernel) should be displayed on chrome://crashes page What happens instead? Kernel crash is not displayed on chrome://crashes page. Please use labels and text to provide additional information. Note: Triggered more than 2 kernel crashes on this device, but from the logs I see only the latest one being displayed. The earlier ones are not getting displayed in the logs. latest Kernel crash ID : e490b48a80000000 earlier Kernel crash ID: 5996785840000000 For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Feb 15 2017
,
Feb 16 2017
,
Mar 6 2017
Snanda@/Dianders@ how should we approach this issue? The crashes are currently no rendering on chrome://crashes page and this is currently a stable blocker for M57. Do we know who should be looking at this?
,
Mar 6 2017
,
Mar 6 2017
is this the only system it's happening on ? or is it all kevins ? looking at that tarball, some of the log files seem like they've been corrupted by a crash. Chrome's UI might not handle that nicely. in which case i don't think this is a regression, so it's not a blocker either.
,
Mar 6 2017
also, if you look at /var/log/messages, you'll see that the chrome & kernel crashes were detected/queued/uploaded properly.
,
Mar 6 2017
thanks vapier@ for confirming. removing RBS.
,
Mar 20 2017
Seems like a general case where we can improve crash reporting. Not an area I'm owning at the moment (though I'm certainly very interested in it!), so removing myself as owner.
,
Jul 26 2017
,
Jul 26
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 17
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by pgangishetty@google.com
, Feb 15 2017