Safari 3.2.1 has been crashing like crazy for me today. I can't imagine what's changed...I haven't installed anything new lately. Crashes about 5-10 minutes after opening. I repaired permissions but no relief. Any advice?

Conficker?

Quote
Tommie Milwaukee
Conficker?

On a Mac?

mine too

My Safari 2 has been crashing when I try to order from Amazon.

You guys need to have a meeting to find out what your systems have in common besides the crashing. The culprit is waiting to be discovered...

Empty your browser caches. The option is in the Safari menu.

Close Safari. Go to Home/Library/Preferences/com.apple.Safari.plist. Drag that to the Desktop. Open Safari. Reset all of your preferences. Try it, If it works, trash the preference file on the Desktop.

If it doesn't, post back here and find out what to do next. If you don't post, we'll assume it worked.

---

Ed (modelamac)

I think I will just put an OUT OF ORDER
sticker on my head and call it a day.

Quote
modelamac
Close Safari. Go to Home/Library/Preferences/com.apple.Safari.plist. Drag that to the Desktop. Open Safari. Reset all of your preferences. Try it, If it works, trash the preference file on the Desktop.

If it doesn't, post back here and find out what to do next. If you don't post, we'll assume it worked.

I once solved Safari crash issues by deleting the Bookmark icons, using Onyx, free app. It's under the tab Cleaning: Internet, I think.

For what it's worth, Safari beta 4 has been rock solid. Not one issue, and I ran the little freeware that straighten's out all the new "better" design features, like tabs at the top, etc. Very good browser. And VERY fast.

---

M1 2020 Mac mini (16G 2T) • Ventura 13.x • Dual 27" Dell S2722QC monitors • M2 2022 13" MBAir (512G 16G) •

How odd, Safari had been crashing on me too. I had added some RAM into my Sawtooth from another Sawtooth, it was a pair of OWCs 256MB sticks, and the crashing started, along with a couple of kernel panics. I replaced one of the 256s with the original 128MB and so far all is well again.

Cheers!

Yep, bad RAM will do it every time.