Q: safari quits unexpectedly

Please launch the Console application in any one 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 and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

          SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

          View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

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

Step 2

In the Console window, select

          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

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 other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

markbet wrote:

 

Process:               Safari

Path:                  /Applications/Safari.app/Contents/MacOS/Safari

Identifier:            com.apple.Safari

Responsible:           Safari

org.adblockplus.adblockplussafari-GRYYZR985A (1.10 - 1.10) Adblock Plus

Performing @selector(safari_printDocument:) from sender NSMenuItem 0x7f9649d136a0

8   com.apple.Safari.framework         0x00007fff9a7d5c7a -[PrintingAccessoryViewController setRepresentedObject:] + 60

13  com.apple.Safari.framework         0x00007fff9a59d57c -[BrowserDocument

 

 

 

The only thing I see is the Adblocker Plus, could this be the problem? If so, what is a safe alternative to Adblocker plus that does not interfere with Safari?

I use Adblock Plus with Safari, and have never had a problem, and while that's purely anecdotal, I don't think that's the problem.

You didn't clear the search box before taking Step 2, so that's not a complete crash report, but you should rule out the Safari extension as a suspect by disabling it. See whether the crashes stop.