Issue metadata
Sign in to add a comment
|
Device is not usable on TOT |
||||||||||||||||||||||
Issue descriptionChrome OS 10678.0.0, 68.0.3429.0 EVE Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)login to user account (2)In a few seconds device freezes and crashed. (3) Expected Result: Actual Result: Device is not usable. Feedback report: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lRFilter=1&lReportSearch=device%20freezes&lROrder=2&lReport=85444744793 How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
May 14 2018
Observed on Coral device ( nasher ) also.Rebooting the machine doesn't help .
,
May 14 2018
Looked at the crash reports from the machine in the feedback report in the description. A large number of crashes in many areas of the system reported over the course of a few seconds. It's difficult to tell what the root cause is, but it looks like the beginning of the cluster is https://crash.corp.google.com/browse?q=clientid%3D%222f81bb92daf84802a1c2ed0b6ae261c1%22&stbtiq=&reportid=ae1f745b93bd5629&index=10 Possibly UI, but I think it makes sense to dig from the kernel side first.
,
May 14 2018
Crash report from eve: https://crash.corp.google.com/browse?stbtiq=2c4c011eabaab987#0
,
May 14 2018
,
May 14 2018
,
May 14 2018
I was able to grab debug logs from a chell device via VT2 right after the hang occurs. Logs here: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/842853
,
May 14 2018
/var/log/messages has many entries of the below warning: session_manager[947]: [WARNING:liveness_checker_impl.cc(64)] Browser hang detected!
,
May 14 2018
,
May 14 2018
xiyuan@, any chance this could be related to the other hang you've been investigating?
,
May 14 2018
,
May 14 2018
"Browser hang detected!" is presented in the original report as well. This means the UI thread is being blocked. The crash http://crash/c0dd5f1e42388ea7 looks suspicious. It is a dong a debug dump on the UI thread and probably holds the UI thread too long. This probably a dup of issue 842505 and the debugging dump is reverted there. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by avkodipelli@chromium.org
, May 14 2018