Safari crashes when opening new tab, add bug report again!

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.

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 a message.

Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor 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.

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. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. 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.

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. The instructions provided by Apple are as follows:

• Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
• When you see the gray Apple logo, release the shift key.
• If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

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.

*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.

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.

Select Safari ▹ Preferences ▹ Extensions from the Safari menu bar. If any extensions are installed, disable them and test.

Select Help ▹ Installed Plug-ins from the Safari menu bar. Besides the following, what plugins are listed?

iPhotoPhotocast

Java

QuickTime

Shockwave Flash

WebKit built-in PDF

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/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.

Step 2

If you still have problems, 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.

Drag or copy — do not type — the following line into the Terminal window, then press return:

rm -fr $TMPDIR../C/com.apple.Safari

Quit Terminal. 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.

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.

Log messages are not a problem in themselves. You will find all kinds of scary log messages on any system, even if it's working perfectly. If the crashes don't come back, you're done.