Issue metadata
Sign in to add a comment
|
Crash reports not uploading |
||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3084.0 (Official Build) canary (64-bit) OS: ChromeOS Pixel v1 What steps will reproduce the problem? (1) Use the browser for a while; it will eventually crash. (2) Visit chrome://crashes. (3) Hit "Start uploading crashes" (4) Check file:///var/log/chrome/Crash Reports What is the expected result? Expect that crash reports are uploaded. What happens instead? No crash reports have been uploaded since April 30th.
,
May 2 2017
click the upload link, then open a tab and watch file:///var/log/messages. crash_sender should output its status there.
,
May 2 2017
Re #2: Device has since auto-updated to 60.0.3086.0, and appears to be uploading crashes normally again (though there are still a few "stuck" in the Crash Reports folder). Log output in messages looks fine; I see a fresh chrome://crash report being uploaded, and then listed in chrome://crashes. Only strange thing was that even though I hit "send", the log indicated that it was "Scheduled to send in 19s" - why would that not be immediate? Sounds like we can close this as obsolete?
,
May 2 2017
it depends on the crash. if it literally just happened, the system gives about 30 seconds for each crash to finish writing its data out. also the crash_sender is a cronjob, so you might have seen it run via that code path which would do a normal sleep schedule.
,
Sep 20
sounds like everything is sorted now ... |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by w...@chromium.org
, May 2 2017