Crashes Users report persistence of crashes under Safari 3.2.1. Hundreds of users reported similar crashes after updating to Safari 3.2, which was released a little more than a week ago.
A sampling of reader reports:
- "Still crashing. Safari 3.2 was crashing, I changed back a version. Tonight I went to 3.2.1 and it has crashed every two or three minutes. Going back again. "
- "PithHelmet still crashes it. AdBlock for Safari works, but I like PithHelmet's contextual selections and the ability to reload unfiltered."
The first workaround you should try when encountering this issue is to turn off the "Warn when visiting fraudulent websites" option in Preferences.
Next, you might need to get rid of Input Managers. Look in the following folders:
- /Library/Internet Plug-Ins
- ~/Library/Internet Plug-Ins
and remove any third-party items.
Possible culprits include PithHelmet, SafariStand and Concierge.
As we stated after the release of Safari 3.2, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for troubleshooting problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must do some cost/benefit analysis. If the functionality of a specific Input Manager or set thereof proves crucial, you may well choose to assume the associated risk.
Slowness Meanwhile, some users report significant slowdown in loading pages and performing other operations under Safari 3.2.1. One MacFixIt reader wries:
"I updated as soon as Software Update said 3.2.1 was available and was sorry within 10 minute. It loads sites extremely slowly. Common sites that I visit that normally load immediately in 3.2 take a very long time in 3.2.1."