Safari 3.1 crashes on 10.4.11 every time!

Question

Anybody experienced 3.1 crashing every time it's opened on 10.4.11??? I've had to give up using it altogether. Any ideas on how to sort this?? Thanks

Answer 1

If your Safari keeps crashing, or if you are updating Safari (or just have):
Input Managers and other plug-ins from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta, and now Safari 3.1. If Safari 3.1 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
(Trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 and 3.1 use a completely different webkit on which other applications like iChat, Mail, Dashboard Widgets etc also rely.)
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Add-on that have been frequently mentioned here, among others, for causing such problems are Piclens, Saft, AcidSearch and Pithhelmet. If you have them, trash them and go the developer's sites to see if new versions are available for Safari 3.1.
You should also ensure, if you are running Tiger 10.4.11, that you have downloaded and installed the correct version for your Mac of Security Update 2008-002. Like all security updates, this requires a restart and a permission repair.
As Leopard also uses Safari 3.0.4, much of the above may well also apply to Leopard, but is not guaranteed. Moreover:
Some users have mentioned that the latest Flash Player (v.9.0.115.0) conflicts with Safari in Leopard, and that they have needed to revert to v. 9.0.47. This can be downloaded from here:
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14266&sliceId=1
To reiterate, 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 problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• /Library/InputManagers
• ~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).