Skip to main content
Home Forums Safari is extremely unstable in Tiger
Safari is extremely unstable in Tiger
· Troubleshooting · 36 posts · May 6, 2005 — Jun 3, 2005 View original thread ↗
Quote:
Originally Posted by Zimphire
I have used a few Safari hacks..

Never crashed on me. Fast, stable.


Ditto, on two Macs. I did an archive and install on both. Using pithhelmet, Safari Enhancer, TinkerTool tweaks and an app that gives a warning if I try to close a page with multiple tabs open.
Quote:
Originally Posted by TETENAL
/Users/stevesweitzer/Library/Application Enhancers/SharedMenus.ape/Contents/MacOS/SharedMenus

/Library/Application Enhancers/Detour.ape/Contents/MacOS/Detour

/Users/stevesweitzer/Library/Application Enhancers/Xounds.ape/Contents/MacOS/Xounds

/Library/Application Enhancers/Instant Hijack Server.ape/Contents/MacOS/Instant Hijack Server

/Users/stevesweitzer/Library/Application Enhancers/Xounds.ape/Contents/PlugIns/Xounds Cocoa Bits.ape/Contents/MacOS/Xounds Cocoa Bits

/Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader

/Library/InputManagers/SIMBL/SIMBL.bundle/Contents/MacOS/SIMBL

/Library/InputManagers/Ecamm/Plugins/DownloadComment.plugin/Contents/MacOS/DownloadComment

/Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu Extra Enabler

/Library/Application Support/SIMBL/Plugins/AcidSearch.bundle/Contents/MacOS/AcidSearch



Try running without all the hacks above and see if the problem goes away. AcidSearch is known to have caused crashes for Safari, but I would try without all the fake InputManager hacks (and if that doesn't help also without the APE-Haxies).



Sorry for the stupid question but what's the best was to remove these hacks? Should I create a "Hacks" folder and put everything in it and then reinstall the origional programs and see what makes it crash?
Quote:
Originally Posted by sesweitzer
Sorry for the stupid question but what's the best was to remove these hacks? Should I create a "Hacks" folder and put everything in it and then reinstall the origional programs and see what makes it crash?

You could rename the folder Input Managers in your Library folder containing them to Input Managers (Disabled) and reboot. Then you use Safari and see if the problem is gone. APE has a control panel that can be used to disable it (but more likely it's the fault of a fake-Input Manager hack).
If you reinstall the programs that installed the hacks, you will reinstall the hack and possible get the problem back. It might be that a newer version is available that fixes the crash.
Bingo... upgrading the programs you pointed out to me solved the problem. Thanks for you help. I've been trying to solve this problem since upgrading to Tiger and you are the first of offer specific advice. Plus, I've learned a lot in the process.

Thanks again,
Steve
Well, I have a new one: my Safari, which has no hacks/input managers suddenly started crashing on me. Safari has been as smooth as those without problems reported here, but all of a sudden, I cannot keep the browser running for more than a minute. Browse to a web page and BAM. Crash! WTF? The weird thing is that I don't even get a crash report dialog. Safari just quits and that's all. No notification.

Console.app reports the following:

Quote:
2005-06-02 23:01:27.786 Safari[342] An uncaught exception was raised
2005-06-02 23:01:27.786 Safari[342] *** -[NSConcreteFileHandle readDataOfLength:]: Input/output error
2005-06-02 23:01:27.787 Safari[342] *** Uncaught exception: <NSFileHandleOperationException> *** -[NSConcreteFileHandle readDataOfLength:]: Input/output error


Any ideas? I have removed all my plug-ins (Flash, Shockwave, Java, PDF, and QuickTime) but still no luck.

[edit] The safari crash log shows no crash-related data. In fact, the last time Safari crashed on my machine was back in March 2004!!!

Quote:
Host Name: maLubie.local
Date/Time: 2004-03-13 10:35:09 -0800
OS Version: 10.3.2 (Build 7D24)
Report Version: 2
[edit] Nevermind what's below...it seems to have fixed itself after ten minutes of thinking...

Buh Jebus! Now because of Dashboard's use of WebKit, it appears none of my widgets work...they just sit there upon invoking the Dashboard, thinking. Great.

mp.ls