Safari 3.0 beta (#7): iChat slowness (cont.) -- workaround; Mail.app slowness, problems accessing; more
Safari 3.0 beta (#7): iChat slowness (cont.) -- workaround; Mail.app slowness, problems accessing; more
iChat slowness (cont.) -- workaround Users continue to report noticeable slowness in iChat after installing Safari 3.0 beta, a problem that may only be soluble through uninstallation of the beta.
One reader writes:
"I have installed Safari 3.x and am noticing the intermittent iChat slowness in sending your site mentions. (Can't confirm on receiving since I don't know when the other person hits enter.) After typing in a message, sometimes when I hit return the text box goes blank like normal, but the message isn't sent until I hit a key (doesn't seem to matter which one). As soon as I do, message gets sent. This happens about 1 in 10 times, I estimate. I have the latest OS build (10.4.9) and security updates, etc."
A less than ideal workaround for this issue is to hit return twice when sending chat messages. Apparently the problem manifests when there are line breaks in the message being sent, and double-tapping return alleviates the slowness.
As reported yesterday, in some cases, these problems are due to third-party iChat add-ons like Chax or ChatFX, which should be removed as a first measure. However, uninstallation with the included Safari3BetaUninstall.pkg appears to be the only viable fix for many users experiencing this issue.
Mail.app slowness, problems accessing Some users are also reporting significant slowness in Mail.app after installing Safari 3.0 beta.
MacFixIt reader Claude M. Cauwe writes:
"I have updated Safari to the 3.0 beta version. Since then, clicking on the 'reply to' or the 'forward to' button in mail takes ages (between 3 and 7 seconds) before the message window appears. (it was instantaneous before) I would even say that it takes a bit longer each time, but couldn't quantify the delay increase."
If you are experiencing a similar issue, please let us know.
Another Input Manager removal success story Yesterday we noted that perhaps the single most effective and broadly applicable fix (as previously recommended) for a bevy of issues under Safari 3.0 beta -- ranging from persistent crashes to problems loading pages to failure to launch -- is to delete any and all Input Managers from the following directories:- /Library/Application Support/SIMBL/Plugins/
- Library/InputManagers
- ~/Library/InputManagers
MacFixIt reader Luigi Chiarani is the latest to find success with removal of these files:
"I gave some input previously regarding trouble with pages loading even after removing AcidSearch and the SIMBL plugins etc. Well I'm happy to report I found what was causing Safari to not load pages when typing a url in the address box, ( unless the url was in the bookmark menu), and also not loading any google searches. I found 'Sogudi' was in my home library, I removed it and all is well. Thanks for your help."
Feedback? Late-breakers@macfixit.com.
Previous coverage:
- Safari 3.0 beta (#6): Reminder: Remove Input Managers; Check for add-on updates; iChat slowness
- Safari 3.0 beta (#5): Will not install/launch: Remove Safari Enhancer, update Speed Download; more
- Safari 3.0 beta (#4): Enhanced 'Reset Safari' function; fix for non-launching apps; more
- Safari 3.0 beta (#3): More serious issues and fixes
- Safari 3.0 public beta (#2): What gets installed; Widgets not working; Input managers can cause problems; more
- Safari 3.0 public beta for Mac OS X released
Resources