Safari: Failue to Launch

December 28, 2006 2:14 PM

Safari 2.04 will not boot on my Dual 2 GHz G5 mac (10.4.8).

I've been using firefox for the past year or so and I'm thinking about moving back. But each time I launch Safari, it crashes.

These are the last few lines of code in the Report dialog box.

0x9a4fc000 - 0x9a532fff com.apple.Syndication 1.0.6 (54) /System/Library/PrivateFrameworks/Syndication.framework/Versions/A/Syndication
0x9a54f000 - 0x9a561fff com.apple.SyndicationUI 1.0.6 (54) /System/Library/PrivateFrameworks/SyndicationUI.framework/Versions/A/SyndicationUI
0xc0000000 - 0xc000ffff com.unsanity.ape 2.0.1 /Library/Frameworks/ApplicationEnhancer.framework/Versions/A/ApplicationEnhancer

I tried to remove the application Enhancer mentioned in the last line to no avail. I'm sure it's a corrupted preference or some unsanity shareware somewhere. I just can't find it. Thanks.

posted by captainscared to computers & internet (7 comments total)

You can remove Application Enhancer from the System Preferences. Also try deleting ~/Library/Preferences/com.apple.Safari.plist
posted by Mwongozi at 2:16 PM on December 28, 2006

Those lines are useless. They're part of the list of what you've got installed.

The actual log of the crash is elsewhere. Look for the lines immediately below "Thread [x] Crashed", which have a log type thing in reverse order.
posted by cillit bang at 2:27 PM on December 28, 2006

Those lines are useless. They're part of the list of what was running at the time of the crash, not to mention APE is pretty much never, ever, ever, at all, ever the cause of application crashes.

The actual stack trace from the crash -- the bit that tells you what the application was trying to do when it croaked -- is immediately under the text "Thread N Crashed" where N is some number.

Chances are it's some outdated SIMBL plugin, something you installed ages ago and broke with a recentish Safari update, but it wouldn't hurt to nuke the prefs, either.
posted by majick at 2:38 PM on December 28, 2006

I'd start by removing all your plugins from the /Library/Application Support/SIMBL/Plugins directory, and seeing if that clears it up. You might also need to check in ~/Library/... and maybe even /System/Library/... just to be sure.

If it still crashes, then I'd delete the preferences. (I'd say try plugins first, because it would suck to hose your preferences if the problem lies elsewhere.)

If that doesn't fix it, then I'd create a new user, reboot and run as that user, and see if it crashes (thus ruling out any user-specific issues such as conflicts with background apps, etc.).
posted by Kadin2048 at 2:54 PM on December 28, 2006

If that doesn't fix it, then I'd create a new user, reboot and run as that user, and see if it crashes (thus ruling out any user-specific issues such as conflicts with background apps, etc.).

You should test under a new user before deleting stuff, honestly. It's quick, it's non-destructive, and it is a qualitative split-half test.

Thirding the "give us the trace for the crashed thread" sentiment.
posted by Mikey-San at 2:56 PM on December 28, 2006

It was an old version of Acid Search.

Thank you.
posted by captainscared at 5:01 PM on December 28, 2006

Still, post the crashed thread excerpt. It may help future troubleshooters solve their issues.
posted by Mikey-San at 6:19 PM on December 28, 2006