New issue
Advanced search Search tips

Issue 601896 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 601457
Owner:
Closed: Apr 2016
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Canary no longer opens after latest OS update

Reported by atlantar...@gmail.com, Apr 8 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/601.6.14 (KHTML, like Gecko) Version/9.1.1 Safari/601.6.14

Steps to reproduce the problem:
1. Tried opening application.
2. 
3. 

What is the expected behavior?
Icon bounces; doesn't open. Have to force quit.

What went wrong?
It won't open.

Did this work before? Yes Two days ago, before latest Mac OS update

Chrome version: 51.0.2703.0  Channel: beta
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 21.0 r0
 
Found this on another website:

Navigate to "[user]/Library/Application Support/Google/Chrome Canary" and delete the "Local State" file in that directory. You should then be able to start Chrome Canary back up.

This did work.
Labels: Needs-Feedback
Thanks for your report.

Does this also happen on 10.11.4?
Also, is there a crash report?
There was no crash report; the application never opened. Chrome Canary worked under OS 10.11.4, but required the deletion of the "Local State" file after upgrading to 10.11.5.

Comment 5 by rsesek@chromium.org, Apr 14 2016

Can you check ~/Library/Application Support/Google/Chrome/Crashpad/completed for any reports from April 8th (or whenever this was happening)?

This may be  issue 601457  which was fixed and is not related to OS upgrades at all, just a broken canary.
There were no files in that folder.

It was possible to fix the application by deleting the "Local State" file (as stated in the original report), so Chrome Canary is working fine now.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 15 2016

Labels: -Needs-Feedback Needs-Review
Owner: ellyjo...@chromium.org
Thank you for providing more feedback. Adding requester "ellyjones@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
I'm going to mark this WontFix. It seems likely that the original profile was corrupt somehow, but without that profile, there's no way to tell if this bug still exists.
Mergedinto: 601457
Status: Duplicate (was: WontFix)

Sign in to add a comment