I ran into an annoying issue with Chrome with a generic installation of MacOS crashing right after launching. After installing it from Google I simply launched the app, as one does. The Chrome logo appears in the dock then yeets itself off somewhere. Sometimes it may generate a crash report, but most of the time it didn’t until I tried to wipe some of the preference folders out to reinstall per Google’s recommendation.
MacOS may generate a crash report with the error: EXC_CORPSE_NOTIFY
Execute corpse notify?
Found an interesting fix that may save someone the frustration of wading through dozens of hits only to never find a solution – like I did for the last hour.
Chrome, why you no launch?
What I found was that Google Chrome is trying to create a folder in the following path:
But the folder security settings are preventing my apps from doing anything in the folder. I’m not sure why, but it’s fecking annoying.
Fix this travesty:
Simply add permissions to this folder for your user account to read and write into the Chrome folder so Chrome can make the subfolders it needs to do its job.
- From the desktop type Command K to launch the Go to folder window
- Enter the following path: ~\Library\Application Support\
- Locate the Google folder
- Right click on the Google folder and select Get Info
- At the bottom right corner, click the Lock icon and authenticate to unlock it.
- Click the + button in the lower left corner to add a user (YOU!) to this list, give yourself read/write access
- Close the window and launch Chrome again.
You’ll notice new folders created in the Google folder and Chrome doesn’t yeet itself any longer.