New issue
Advanced search Search tips

Issue 608426 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Google Chrome Unstable 52.0.2716 crashs linux desktop

Reported by brookha...@gmail.com, May 2 2016

Issue description

Chrome Version       : google-chrome-unstable-52.0.2716
URLs (if applicable) :
Other browsers tested:
 Locks machine, disks go offline

have tested this issue:
No debugging available, linux os hangs, disks go offline, no messages in systemd

What steps will reproduce the problem?
Load google-chrome-unstable google-chrome-unstable-52.0.2716

What is the expected result?
Not to have PC crash.

What happens instead?
Disks go offline, systemd errors cant see disks, using XFS file system.

Please provide any additional information below. Attach a screenshot if
possible.
Only happens with google-chrome-unstable-52.0.2716

 
Labels: OS-Linux
If your PC is crashing, it's more likely you are having hardware issues.
Its not the PC, I've been troubleshooting, appears to be the profile in .cache/google-chrome-unstable. 

I've never debugged chrome before, so I found a --diagnostics command line.

On the current broken profile it fails on 2 things
[FAIL] User preferences integrity
       File too big
[FAIL] Thumbnails database
       Cannot open DB. Possibly corrupted

If I remove the .cache/google-chrome-unstable directory, google unstable starts fine and runs. Something is broken in the that cache directory...

I'll keep troubleshooting, but it is the browser.

If I tar the broken cache directory, I get a "Cannot savedir: Structure needs cleaning"
Looks to be a bad cache file on disk thats chrome is triggering the OS.  Will try a xfs repair and see if that fixes the issue.   Not sure how chrome is triggering the file subsystem, tar isnt. 
Yup, corrupted file in .cache/google-chrome-unstable, did an xfs repair and that fixed the file, unstable working again.
Status: WontFix (was: Unconfirmed)
Thanks for the update, closing this issue for now.
Please raise  separate issue if you have any issue using chrome in future.

Sign in to add a comment