Skip navigation

TS3230: Safari: Unsupported third-party add-ons may cause Safari to unexpectedly quit or have performance issues

Learn about Safari: Unsupported third-party add-ons may cause Safari to unexpectedly quit or have performance issues

TS3230 This is not helping me at all, I'm not sure what third party add on to uninstall

290 Views 2 Replies Latest reply: Jun 13, 2013 12:47 AM by Linc Davis RSS
fford Calculating status...
Currently Being Moderated
Jun 12, 2013 10:30 PM

I keep getting the unexpected error and it won't let me in safari

I've tried everything else on here and nothing is working

iMac, OS X Mountain Lion (10.8.4)
  • Carolyn Samit Level 10 Level 10 (84,150 points)

    You need to look at all the Library folders from the link you posted from.

     

    • /Library/Internet Plug-Ins/
    • /Library/Input Methods/
    • /Library/InputManagers/
    • /Library/ScriptingAdditions

     

    • ~/Library/Internet Plug-Ins/
    • ~/Library/Input Methods/
    • ~/Library/InputManagers/
    • ~/Library/ScriptingAdditions

     

    The first four locations listed are in the root-level Library on your hard disk, not the user-level Library in your Home folder.

    The tilde (~) represents your Home folder.

  • Linc Davis Level 10 Level 10 (107,760 points)

    Launch the Console application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

     

    Step 1

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

    Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).

     

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

     

    Step 2

     

    Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
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.