Skip navigation
This discussion is archived

New version 1.3.1 (v312.3) continuously crashes 0n 10.3.9

492 Views 31 Replies Latest reply: Sep 11, 2005 6:58 PM by Kris Jones RSS
  • iBod Level 7 Level 7 (29,340 points)
    Hi TWW,

    Can you post the crash log for us to look at? It will take a few posts due to it's length but they often contain hints on what's going wrong (especially when it happens in just one user account).
  • Kris Jones Calculating status...
    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.

    I hope this helps.
  • iBod Level 7 Level 7 (29,340 points)
    Hi again,

    Can you post the full log - don't worry about the number of posts it takes

    There's not enough information in the above to see what may be the problem.
  • iBod Level 7 Level 7 (29,340 points)
    Hi TWW,

    This thread has an example of the full crash log (the above only shows the very end of the report):

    iBod, "Safari 2.0 Won't Launch" #3, 04:21am Aug 21, 2005 CDT

    The text file itself with this information can be found at /Users/YourUsername/Library/Logs/CrashReporter/Safari.crash.log

    If you'd like to email me that file, feel free. You can find my email by clicking on my alias name to the left.
  • iBod Level 7 Level 7 (29,340 points)
    Message received and reply sent!

    Let us know if that was the problem in the end.
  • Kris Jones Level 1 Level 1 (55 points)
    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.
  • Barry Hemphill Level 7 Level 7 (33,085 points)
    Hello 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.

  • Dedo Calculating status...
    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/ * Warning: ATSUSetFontFallbacks has been deprecated. Use ATSUFontFallbacks objects instead. *"
  • Tom Graves Level 7 Level 7 (20,615 points)
    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.
  • Dedo Level 2 Level 2 (205 points)
    Sorry.....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 see there's even a term for it............threadjacking. I'd delete that post if I knew how.

    I started my own topic.


More Like This

  • Retrieving data ...

Bookmarked By (0)

This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.