Q: Utility Disk crashes after opening Safari

backup

boot into Recovery mode

repair the drive

you could have bad file, preference, trouble with your system

Safari and Safari.web.content (Activity Monitor) can eat up a couple GBs of RAM which should not be a problem assuming you have "enough"

have you tried boot Safe Mode?

TimeMachine 101

https://support.apple.com/kb/HT1427

Mac OS X & Mountain Lion Community

https://discussions.apple.com/community/mac_os

https://discussions.apple.com/community/mac_os/os_x_mountain_lion?view=discussio ns

Recovery Mode

http://support.apple.com/kb/HT4718

General purpose Mac troubleshooting guide:

Isolating issues in Mac OS X

Creating a temporary user to isolate user-specific problems:

Isolating an issue by using another user account

Identifying resource hogs and other tips:

Using Activity Monitor to read System Memory and determine how much RAM is being used

Starting the computer in "safe mode":

Mac OS X: What is Safe Boot, Safe Mode?

To identify potential hardware problems:

Apple Hardware Test

General Mac maintenance:

Tips to keep your Mac in top form

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.