Issue metadata
Sign in to add a comment
|
Chrome app not start on cranky machine which just forgot all keychain passwords
Reported by
tomach...@gmail.com,
Sep 20
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15 Steps to reproduce the problem: 1. Double click the icon. It animates to open but never appears in the dock. 2. Attempting to open from terminal using open /Applications/Google\ Chrome.app/ returns quickly with the message shown. 3. Experience a hard crash / hard reset, then disk verify and repair. 4. Also experience loss of the keychain so I now need to enter passwords for: ssh, network servers, google backup etc, anything that uses macOS secure password storage i guess. i think my machine has hardware issue. is well used laptop about to have OS re-installed due to..... something is causing it to use virtual memory / swap but it has 16 GB ram. What is the expected behavior? chrome browser should open and present a window. What went wrong? LSOpenURLsWithRole() failed with error -10810 for the file /Applications/Google Chrome.app. Crashed report ID: no sorry How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes the version i pasted in the issue - taken from server logs Chrome version: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36" Channel: n/a OS Version: OS X 10.12.6 Flash Version: hard to say - chrome won't startup - it is installed though probably my machine. about to re-install the OS for many reasons.
,
Sep 20
FYI ~ ❯❯❯ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome [1] 23948 killed /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome It would appear that I have 23,000 processes open. 6039 lines showing on lsof. It might also be this process that is crashing: /System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
,
Sep 20
RESOLVED: Reinstall Chrome. Issue solved. Was likely an issue with my machine only.
,
Sep 21
As per comment#3, closing this issue. Thanks! |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by tomach...@gmail.com
, Sep 20