Mac OS X 10.3.9 #2: Safari crashes on launch; Broken JavaScript, java; solutions

Safari: Crashes on launch, broken JavaScript, Java

Crashes on launch A number of users report that Safari is crashing on launch after updating to Mac OS X 10.3.9.

This problem, in most cases, is caused by an apparent problem with the new version of Safari's ability to handle additions to the Library/Application Support/SIMBL/Plugins folder.

These include popular shareware utilities like AcidSearch and Pith Helmet.

Removing these items from the above folder (e.g. acidsearch.bundle) will resolve the on-launch crashes in most cases.

Several readers have also noted that clearing system caches with a tool like OnyX or Panther Cache Cleaner. Select "Delete all caches" or a "deep" cache clean, dependent on which tool is being used. After deleting caches, use Apple's Disk Utility (Applications/Utilities) to repair permissions.

Broken JavaScript Some popular Web sites that make use of JavaScript are no longer working properly in Safari for some users since installing Mac OS X 10.3.9. These include a number of banking Web sites, and several of Google's tools.

MacFixIt reader Amuro Ray writes:

"Access to Google's Gmail is no longer possible after the Mac OS X 10.3.9 upgrade. The login page will still show normally. The problem, however, is that once you've 'successfully' logged in, Safari will crash (with the spinning ball) immediately. I have waited for a few minutes (with the spinning ball), and have finally forced to force quit Safari. Turning off JavaScript will allow me to login to my G-mail successfully, although Gmail will now tell me that my browser is not enabling all of its features (obviously, JavaScript)."

As noted in Knowledge Base article #301327, the version of Safari included with Mac OS X 10.3.9 includes a significant security update affecting JavaScript. According to Apple:

"This update closes a vulnerability that allowed remote websites to load javascript to execute in the local domain."

As such, turning off JavaScript (in the Security pane of Safari's preferences) will allow some problematic sites to be accessed, albeit in limited form.

Another alternative is to set Safari's user agent to a different browser. This is accomplished by first activating the Safari debug menu (most easily with a tool like Safari Enhancer) then selecting "Windows IE" or another agent.

MacFixIt reader David Benesch writes:

"Unfortunately, the first website I visited after updating to OS X Mac OS X 10.3.9 was maps.google.com. The new version of Safari (1.3) displays many things incorrectly. If another User Agent (like Windows IE) is selected via the debug menu, the site renders fine. I suspect that Google had to work around a rendering bug in Safari that is now fixed, but the fix no longer works correctly in the new Safari. I've tested this on two machines. Otherwise, 10.3.9 works fine for me."

Broken Java A number of readers are reporting that Java applets cause Safari to crash after updating to Mac OS X 10.3.9. This problem can generally be worked around by re-installing the most recent Java updater (Java 1.4.2 Update 2).

However, for many users, the Java update installer refuses to do its job because -- for some reason -- it does not recognize that there is an installed version of Java to be updated.

As noted by one MacFixIt reader:

"Java programs don't work (under Mac OS X 10.3.9). Typing 'java -version' in Terminal gives a segmentation fault. Trying to reinstall Java 1.4.2 v2 doesn't work, as it doesn't recognize that the installed version of Java can be upgraded."

Luckily, there is a workaround for this issue. Though the Java update installer refuses to properly place components, you can use a utility like unpkg to extract the various parts of the Java 1.4.2 update 2 package, and drag and drop the components to their appropriate locations.

MacFixIt reader Josh Camp writes:

"I was having the same problem as everyone else, any time safari try's to load a java applet it would crash Safari. The way I got around it was to reinstall the java142update2. Of course the installer would not let me so I used a free app called unpkg which unpacked it to my desktop. I then just did the drag and drop thing, and just like that Safari works with Java applets again. "

In order to perform this workaround, first download unpkg. Next download the Java 1.4.2 Update 2. Drag the file Java142Update2.pkg -- which now should be located on the mounted Java 1.4.2 Update 2 disk image -- onto the unpkg icon.

The files contained in the package will now be located on your desktop in a folder named Java142Update2. The files in this folder will be organized according to where they should be placed on your startup volume. For instance, you will see a Library folder, within which you will find folders named "Internet Plug-Ins" and "Java." Drag the individual files located in these folders to the to the folders /Library/Internet Plug-Ins and /Library/Java respectively.

When performing these procedure, copy at the file level only. In other words, do not attempt to copy an entire folder (e.g. the "Library" folder located in the Java142Update2 folder) or vital components may be deleted. You can drag multiple individual files simultaneously, but do not attempt to replace entire folders.

Another workaround that has proved successful for some readers is simply re-installing Security Update 2005-002, which includes changes to several Java components.

The age-old method of re-applying the Mac OS X combination updater has also resolved Java issues for some readers.

Positive reports MacFixIt reader Scott Leddy, though experiencing the aforementioned Java crashes, welcomes a fix for excessive fan noise that was occurring after Mac OS X 10.3.8.

Leddy writes:

"Just to let you know that Mac OS X 10.3.9 thankfully fixed the well described fan issue that 3.8 created with many dual G5's. Also, issues 3.8 created on my machine such as locking up upon awaking from sleep seem resolved with 3.9 as well. However, Safari does crash the instant I load a Java applet, as some other users have reported.

Feedback? Late-breakers@macfixit.com.

Resources