Safari 3.2.1 (#2): more crash fixes

Safari 3.2, released a few weeks ago, has been prone to crashes when users attempt links in tabs. The release of Safari version 3.2.1 specifically addresses the issue of crashes pertaining to opening links in new tabs. While this has solved crashing problems for some users, it has not for all users. Some users have found that certain pop-up window behavior still causes the program to crash, regardless of whether or not popup blocking is turned on (see our previous coverage).

Apple Discussions poster Raymond Smith writes:

"3.2.1 still crashed for me. U dud the auto update, repaired disk permissions, and started surfing the APPLE STORE (how ironic). I clicked on iPod Touch, clicked on "laser engraving" icon. A smaller window started to appear (a pop up)... crashed - multiple time - same sequence."

It should be noted that while this update fixes a prominent cause for crashing in Safari 3.2, there are other causes for Safari crashing which have known fixes.

More Fixes

Reset Safari Users who're experiencing persistent crashing in Safari should first reset Safari using the option in the "Safari" menu. It is recommended to check all options to reset and hopefully this will fix the problem.

Remove Input Managers As described previously, users might try removing any input managers installed in the mentioned folders. Additionally, users might try disabling the new anti-phishing features in Safari 3.2.x.

Delete the history plist file Some users have cured certain crashes by removing Safari's history file, which is located in the /username/Library/Safari/ directory and is called History.plist. Upon removing this file, Safari will create another one. Beyond just this file, users may also try removing others in the same "Safari" directory. It is recommended to first back up these files, as they may contain important information such as bookmarks.

Remove the Safari cache database While resetting Safari should empty and reset the caches, it is possible that corruption in the database file could prevent it from being accessed properly, even for emptying. As such, users should try removing it manually by entering the following command in the terminal (copy and paste):

rm $(getconf DARWIN_USER_CACHE_DIR)com.apple.Safari/Cache.db

Feedback? http://www.macfixit.com/contact.

Resources