I may have figured out Safari crashing on Yosemite...

[aquila421]

Tried relentlessly to pinpoint the Safari issue. Im my case, it wasn't RAM, it wasn't CPU, but actually Safari claiming all unused HD space. Trust me, I still don't understand.

Long story short, I eventually tried this command in terminal:

mv /Users/username/Library/Caches/com.apple.Safari /Users/username/Library/Caches/com.apple.SafariOLD

Somehow, someway, I've been stable since.

Can anyone confirm?

PS, first post here. Hi all.

 

[The19th]

I'm not currently having any issues in Safari, but I cleaned up the terminal command to make it more generic, since not everyone has "username" as their Mac OS X account name.

mv ~/Library/Caches/com.apple.Safari ~/Library/Caches/com.apple.SafariOLD

Additionally, I wonder if simply renaming it in the Finder would work before resorting to a terminal command:

• Option-click the "Go" menu in the Finder, then select Library and navigate to Caches and rename the com.apple.Safari folder from there.
• or press Command-Shift-G for Go to Folder… enter "~/Library/Caches" (without quotes) and rename the com.apple.Safari folder from there.

 

[melburstein]

Tried relentlessly to pinpoint the Safari issue. Im my case, it wasn't RAM, it wasn't CPU, but actually Safari claiming all unused HD space. Trust me, I still don't understand.

Long story short, I eventually tried this command in terminal:

mv /Users/username/Library/Caches/com.apple.Safari /Users/username/Library/Caches/com.apple.SafariOLD

Somehow, someway, I've been stable since.

Can anyone confirm?

PS, first post here. Hi all.

I regret to report that this did not solve the problem for me. I still get a Kernel Panic (see attached) every time an attempt is made to open Safari.

 

[boast]

Crash log shows it seems either your icloud local or icloud web database of your history is corrupt.

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** setObjectForKey: object cannot be nil (key: URL)'

Looks like they use a hash table with the URL being the key. Somewhere there is an empty URL, and they didn't program Safari to catch the error, so the entire program crashes.

I assume you already made a bug report on this, right?

 

[melburstein]

Crash log shows it seems either your icloud local or icloud web database of your history is corrupt.

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** setObjectForKey: object cannot be nil (key: URL)'

Looks like they use a hash table with the URL being the key. Somewhere there is an empty URL, and they didn't program Safari to catch the error, so the entire program crashes.

I assume you already made a bug report on this, right?

Yes, I have submitted a report to Apple .

Is there anything I can do? Or do just have to wait?

Thank you for your useful analysis.

 

[HarryT]

I saw this too.

I used DaisyDisk because it said my startup drive was almost full - which was weird.

Safari Cache had claimed 28gb of drive space. I simply deleted it in DaisyDisk and since then its been ok!

 

[boast]

Yes, I have submitted a report to Apple .

Is there anything I can do? Or do just have to wait?

Thank you for your useful analysis.

Does Safari launch if you go to System Settings > iCloud > Safari and disable it?

 

[chrfr]

I regret to report that this did not solve the problem for me. I still get a Kernel Panic (see attached) every time an attempt is made to open Safari.

Note that what you have is a crash in Safari, not a kernel panic.
Does Safari crash in a different user account? Also, start the computer in safe mode once, then restart and try Safari again. Failing that, delete all the preferences for Safari.

 

[inket]

Yes, I have submitted a report to Apple .

Is there anything I can do? Or do just have to wait?

Thank you for your useful analysis.

If you have another OS X installation with a working Safari, open Safari there and clear History. (Does browser history even sync ? I only have one Apple device so I don't know)

The stack trace mentions "Cloud History", anyways.

If that doesn't work, you could try exporting your favorites & reading list, then clearing them so that there's nothing to sync and no reason to crash.

 

[HowEver]

The latest beta completely fixed the constant Safari crashing for me, finally.

 

[melburstein]

Does Safari launch if you go to System Settings > iCloud > Safari and disable it?

I could no find System Settings, but I was able to go to
System Preferences > iCloud > Safari
and remove the check mark from Safari.

Good News: I was able to launch Safari.
Bad News: As soon as I click on the address bar, I get a spinning pinwheel.

So, I think your suggestion works; but now I have a new problem.

 

[melburstein]

The latest beta completely fixed the constant Safari crashing for me, finally.

So, how do I get the latest beta? I am not a developer, but I did subscribe to the public beta.

 

[melburstein]

I saw this too.

I used DaisyDisk because it said my startup drive was almost full - which was weird.

Safari Cache had claimed 28gb of drive space. I simply deleted it in DaisyDisk and since then its been ok!

I have downloaded DaisyDisk (it is worth the $10 bucks).

 

[melburstein]

Note that what you have is a crash in Safari, not a kernel panic.
Does Safari crash in a different user account?

Thank you for correcting me. I like to use the correct terminology. I appreciate your positive comment.

 

[melburstein]

I could no find System Settings, but I was able to go to
System Preferences > iCloud > Safari
and remove the check mark from Safari.

Good News: I was able to launch Safari.
Bad News: As soon as I click on the address bar, I get a spinning pinwheel.

So, I think your suggestion works; but now I have a new problem.

Drawing from a post in another thread, I did two MORE things:
(1) Reset Disk Permissions using the Apple Disk Utility.
(2) sudo update_dyld_shared_cache -force

It worked. Safari Launches. No Pinwheel. THANK YOU boast. THANK YOU macuser1232. Thank you everyone.

 

[psudo]

Thankyou

I'm a mac noobie and the suggestions in this thread solved my safari issues. Thank you!