New version 1.3.1 (v312.3) continuously crashes 0n 10.3.9
Called Apple support. Cleared caches, preferences, etc. still no results. Installed a new user, still no result.
After fooling around for 45 minutes Apple disconnected and did not call back. He was ready to have me start Software Restore 1.
Never had any trouble with previous version. The crash does not affect anything else. I am restarting Safari 20-30 times a day.
It;s very likely that the crashes are being caused by SIMBL plug-in, such as AcidSearch or Pith Helmet. I'm troubleshooting the same issue with Safari 2 on Tiger, and have yet to establish which of those is causing the crash.
If you have AcidSearch, it is most likely installed in Home/Library/Application Support/SIMBL/Plugins. Remove it to the trash and see if that resolves the problem. If it was installed for all users, you'll need to check for it using a similar file path at Macintosh HD/Library too.
If you have Pith Helmet installed you may find it using the same file path as above (though since I've removed that first, I can't check it).
If neither of the above are installed, then it may be another component that you have added, such as Speed Download.
The total crash log is 52 pages. I tried to copy it and post it but the forum would only accept 1 1/2 page. It does not seem practical to send it all unless you think it is .
I could E-mail it to you if you are willing.
Regards
TWW
OK I can understand your frustration, especially as I'm having difficulties with Safari myself. A brief look at your truncated crash report makes me suspect that maybe you've installed a component to view PDF files that might be the cause of the trouble. However, if you've got the (52 page?) crash report saved, it might help if you could locate the section that starts with a sub-heading "Binary images". This will show any additional components that might be installed in support of Safari (I mentioned earlier some of the obvious ones, but you might have something to display PDFs or provide shortcuts when you type in the address bar). It's almost certain that the source of your problem is an additional component to add functionality to Safari, rather than Safari in its raw form, that is causing the constant crashes.
Thank you for everybody's help. The problem was identified in the Safari Crash Log. Ben Thompson advised me that non-Apple applications usually create such problems. Others have listed applications which I did not have.
My problem was IGetter. After removing it Safari works as before.
The Forum has been of great help.
The question remains why Apple tech support can not think of this before marching in with heavy artillery and destroy everything in sight hoping it will destroy the culprit?
Best regards
TWW
I am no apologist for a corporation, but how do you deduce that Apple (or any of the rest of us) could determine you had third party applications installed that amount to haxies? That information was certainly not contained in any of your posts. In fact you said
No third party material was added
Most trouble shooting approaches would suggest removing "non-standard" applications as a first step.
I am also having trouble with Safari 1.3.1 only since I updated yesterday or the day before. The application launches but page loading is in stages........very slow, and I'm never sure it will complete. I also get a lot of question marks on some pages as they try to load. I've added nothing else since updating from 1.3.0 which ran fine. This is my default browser and it seems to be getting worse.
I saw the earlier note about checking for duplicate fonts so I did; I have none. I ran permissions before and after updating Safari; also tossed the .plist
I checked the system log and found this entry shown below; it's in there several times. Is this the problem? Could someone please tell me what it means and what I should do to correct it? Thanks.
"Sep 11 21:15:09 dcn241-58 /Applications/Safari.app/Contents/MacOS/Safari:
* Warning: ATSUSetFontFallbacks has been deprecated. Use ATSUFontFallbacks objects instead.
*"
You will get much more attention if you start a new topic about your problem rather than tack it onto a topic concerning someone else's problem. More people will see it that way. By tacking it onto someone else's problem, people will only stumble on your problem accidently. Also, you asking about a different problem does not help find a solution for the person in this topic.
I didn't view it as new problem or thread but as a variation of the continuing problem with Safari update 1.3.1.
I can understand that, but your symptoms are different enough than what is being discussed in the rest of the topic that a new topic will let more people see that you have a problem - and thereby give more people a chance at giving you a solution. No harm done, just make a new topic if you haven't already.