New issue
Advanced search Search tips

Issue 645844 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chrome OS Crash

Reported by cjpeer...@gmail.com, Sep 12 2016

Issue description

Chrome Version       : Chrome OS - 
Google Chrome	52.0.2743.116 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested: None
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1) Unknown amount of time when Chrome OS crashes. Unable to verify what the cause is.
(2)
(3)

What is the expected result? Crashes and asks to restore.


What happens instead?


Please provide any additional information below. Attach a screenshot if
possible. I was on the dev channel when I started having issues with keyboard lag and thought maybe the Dev channel could be causing the lag. Switched back to the stable channel which included a powerwash and the problem continued. I did another powerwash with no changes. Then I used the recovery tool to reinstall the software and there was still no change. I created another new gmail/google account and did not have any problems. I removed apps and extensions and no changes. 
Attaching log file.
 
debug-logs_20160911-211823.tgz
333 KB Download
debug-logs_20160911-211816.tgz
333 KB Download
debug-logs_20160911-211753.tgz
332 KB Download
Labels: OS-Chrome
Labels: Needs-Feedback
You mentioned "I created another new gmail/google account and did not have any problems" so the issue seems to be related to your account? Can you confirm if you are still seeing this?

Comment 3 by cjpeer...@gmail.com, Oct 11 2016

Yes I was still having the problem. I haven't been in the other account for
sometime now.
Status: Untriaged (was: Unconfirmed)
Can you go to chrome://crashes and upload your crashes and paste the crash numbers here?
Status: WontFix (was: Untriaged)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Sign in to add a comment