Skip navigation

Safari 6.0.5 crashes just after launch

1526 Views 26 Replies Latest reply: Dec 20, 2013 5:40 PM by Dorje RSS
  • nbar Level 5 Level 5 (6,480 points)
    Currently Being Moderated
    Jul 24, 2013 11:34 AM (in response to Jill1230)

    Try removing the following property list files:

     

    ~/Library/Preferences/com.apple.Safari.plist

    ~/Library/Preferences/com.apple.WebProcess.plist
    ~/Library/Preferences/com.apple.WebKit.PluginProcess.plist
    and
    ~/Library/Preferences/By Host/com.apple.Safari.........plist

     

     

    Reboot and test.

  • Linc Davis Level 10 Level 10 (107,375 points)
    Currently Being Moderated
    Jul 24, 2013 11:54 AM (in response to Jill1230)

    Please read this whole message before doing anything.

     

    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    Step 1

     

    The purpose of this step is to determine whether the problem is localized to your user account.

     

    Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

     

    While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

     

    Test while logged in as Guest. Same problem?

     

    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

     

    *Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

     

    Step 2

     

    The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, or by corruption of certain system caches.

     

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.

     

    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and Wi-Fi on certain iMacs.  The next normal boot may also be somewhat slow.

     

    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

     

    Test while in safe mode. Same problem?

     

    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

  • nbar Level 5 Level 5 (6,480 points)
    Currently Being Moderated
    Jul 24, 2013 12:03 PM (in response to Jill1230)

    From finder > Go > hold down the OPT key. Library should show up. Select it > Navigate to Preferences folder. Check again.

     

     

    ~ (tilde) indicates User/username/

     

    ~/Library is different from both /Library and /System/Library

     

    Sorry for the confusion. Try again.

     

    Alternatively, just click the finder icon and hold down the key combination shift-cmd-G.

     

    Enter ~/Library/Preferences/ in the path of the window that opens.

  • Linc Davis Level 10 Level 10 (107,375 points)
    Currently Being Moderated
    Jul 24, 2013 1:01 PM (in response to Jill1230)

    Step 2?

  • nbar Level 5 Level 5 (6,480 points)
    Currently Being Moderated
    Jul 24, 2013 1:39 PM (in response to nbar)

    Results of Step 1

     

    Safari did NOT crash when I logged in as a Guest User.

     

     

     

    Disregard AHT.

     

    Remove the property list files indicated above.

  • Linc Davis Level 10 Level 10 (107,375 points)
    Currently Being Moderated
    Jul 24, 2013 1:39 PM (in response to Jill1230)

    Read this whole message before doing anything.

     

    Back up all data.

     

    Quit Safari if it’s running. Then select

     

    Force Quit…

      

    from the menu bar. A small window will open with a list of running applications. Safari may appear in that list, even though you quit it. If so, select it and press return. Close the window.

     

    Step 1

     

    In the Finder, press the key combination shift-command-A to open the Applications folder. Select the Safari icon in that folder and press the key combination command-I to open the Info window. There’s a checkbox in the Info window labeled Open in 32-bit mode. Uncheck it, if checked. Close the Info window and the Applications folder.

     

    If Adobe Flash Player is installed, select

      

     ▹ System Preferences ▹ Flash Player Advanced

      

    and click Delete All. Close the preference pane.

     

    Hold down the option key and select

      

    Go Library

      

    from the Finder menu bar. Delete the following items from the Library folder (some may not exist):

     

    • Caches/com.apple.Safari
    • Caches/com.apple.WebKit.PluginProcess
    • Caches/com.apple.WebProcess
    • Caches/Metadata/Safari
    • Preferences/com.apple.WebKit.PluginHost.plist
    • Preferences/com.apple.WebKit.PluginProcess.plist
    • Saved Application State/com.apple.Safari.savedState

     

    Leave the Library folder open. Try Safari again. If it works now, stop here. Close the Library folder. If you still have problems, continue.

     

    Step 2

      

    Triple-click anywhere in the line below on this page to select it:

     

    open $TMPDIR../C

     

    Copy the selected text to the Clipboard (command-C).

      

    Quit Safari again. Launch the Terminal 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 Terminal in the icon grid.

     

    Paste into the Terminal window (command-V). A folder should open. If there's a subfolder with the name "com.apple.Safari", delete it, even if it's empty. Quit Terminal. Close the folder. Launch Safari and test.

     

    Step 3

     

    If Safari still doesn’t work right, quit, go back to the Finder and move the following items from the open Library folder to the Desktop (some may not exist):

     

    • Cookies/Cookies.binarycookies
    • Internet Plug-Ins
    • Preferences/com.apple.Safari.LSSharedFileList.plist
    • Preferences/com.apple.Safari.plist
    • Preferences/com.apple.Safari.RSS.plist
    • Preferences/com.apple.WebFoundation.plist
    • PubSub/Database
    • Safari

     

    (Note: you are not moving the Safari application. You’re moving a folder named “Safari.”)

     

    Try again. This time Safari should perform normally, but your settings and bookmarks will be lost. The default set of bookmarks will be restored. Delete them all.

     

    If the issue is still not resolved, quit Safari again and put all the items you moved to the Desktop back where they were, overwriting the newer ones that may have been created in their place. You don’t need to replace the files you deleted in step 1. Stop here and post again.

     

    If Safari is now working normally (apart from the lost settings), look inside the “Safari” folder on the Desktop for a file named “Bookmarks.plist”. Select

      

    File Import Bookmarks

      

    from the Safari menu bar. Import from that file. Recreate the rest of your Safari settings. You can then delete the items you moved to the Desktop.

     

    Note: This step will remove your Safari Extensions, if any, and their settings. If you choose to restore them, do so one at a time, testing after each step to make sure you haven’t restored the problem.

     

    If you don’t like the results of step 3, you can undo it completely by quitting Safari and restoring the items you moved or deleted in that step from your backup, overwriting any that were created in their place.

  • Dorje Calculating status...
    Currently Being Moderated
    Dec 20, 2013 5:40 PM (in response to Linc Davis)

    I had a similar issue on both of my machines (MBP 17" 2011 and MBA 13" 2013).  Did all of the steps you suggested even manually resetting permissions on the applications directories on each machine. Safari worked until I shut down the machines then cold booted them back up.  Safari crashed each time I tried this, even with all extension off or completely uninstalled.  Then I noticed an item in the Safari menu - "About Glims". 

     

    After much rooting around in the user and main Libraries I managed to finally dump all extensions, prefs, caches, etc related to Glims.

     

    Then I re-did your list of hacks and finally Safari seems to be working nominally - with the few extensions I use.

     

    This took the better part of several days to "fix".  One has to wonder about Safari's usefulness.  I don't have these issues with Firefox or Chrome.

     

    Thanks for the tips.

1 2 Previous Next

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.