Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Safari keeps crashing/freezing after install of El Capitan

After the install of El Capitan, Safari 9.0 keeps locking up and or crashing.

I have a Mac Book Pro 15'' 2.3 GHz i7, 4GB Memory, 500 GB HD, iOS 10.11


When using Safari, I will have class work up and YouTube or iTunes playing. Before El Capitan it would do those processes with out a problem. Now it seems to lock up, unable to refresh, unable to exit Safari. I have to force quit and shutdown to try and get control back. Occasionally even after the shut down it will still lock up.

MacBook Pro (15-inch Mid 2012), OS X El Capitan (10.11)

Posted on Oct 14, 2015 10:06 AM

Reply
558 replies

Mar 6, 2018 8:11 AM in response to 49_FiveWindow

Hi there. Same problem with safari crashing the entire system. I've bought Macbook Pro 13" one month ago!. So model is early 2015. When I watch a video in Youtube, the screen freezes and then the entire computer becomes unresponsive and I need to restart. That happens every week and unfortunately the Telephone Support say all the usual stuff that every knows, ie clear caches, restart, SMC, disable plugins etc. Unfortunately the problem started again today after a week.

So I just post here the problem, hoping that Apple will understand that is a VERY BIG problem. A software (Safari) crashes the ENTIRE hardware (computer). That is not normal.

By the way, how can someone see those crash reports, you all refer to.

Thank you

Oct 14, 2015 1:29 PM in response to 49_FiveWindow

Hi, 49_FiveWindow.


Thank you for visiting Apple Support Communities.


I understand that Safari will quit unexpectedly when using various processes on your Mac. I would recommend going through the troubleshooting steps in the article below. You may need to completely remove any extensions or plug-ins to see if this resolves the issue as this could be the cause.


If Safari is slow, stops responding, quits unexpectedly, or has other issues


Cheers

Oct 14, 2015 2:42 PM in response to 49_FiveWindow

Safari/Preferences/Advanced - enable the Develop menu, then go there and Empty Caches. Quit/reopen Safari and test. Then try Safari/History/Show History and delete all history items. Quit/reopen Safari and test. You can also try try Safari/Clear History…. The down side is it clears all cookies.Doing this may cause some sites to no longer recognize your computer as one that has visited the web site. Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Library./Caches/com.apple.Safari/Caches.db and move it to the trash.


Go to Safari Preferences/Extensions and turn all extensions off. Test. If okay, turn the extensions on one by one until you figure out what extension is causing the problem.


Safari Corruption See post by Linc Davis

Oct 14, 2015 9:17 PM in response to 49_FiveWindow

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

Nov 2, 2015 2:05 PM in response to 49_FiveWindow

Having exactly the same problem. Safari locks the whole system down. It just freezes for a few minutes and then resumes, but Safari is heavy and slow.

Before El Capitan everything worked fine. I'm on newest El Capitan 10.11.1 and the problem is still there. That cookie and cash tips can't be the issue.


Really ****** of by this, its a newer macbook 15' and it behaves like a 95 PC when Safari is opened.

Switching to google chrome until some major update goes out

Nov 13, 2015 11:03 AM in response to 49_FiveWindow

Well, the Malware removal app didn't fix the issue. I haven't had an issue for a couple of days with Safar...but we started playing back YouTube videos and everything fell apart AGAIN!


Safari and YouTube are disaster together. It's got to be a Safari issue because I have NO issues with Chrome. This is bringing the entire system to a crawl. Logging in here took forever. I watched as it took 3-5 seconds to show each letter of my login.

Nov 13, 2015 12:19 PM in response to 49_FiveWindow

The idea to examine my extensions led me to notice that I was using a somewhat older version of FastestTube. Since I too was mostly experiencing the issue when switching to YouTube tabs, I tried installing the newest version of the extension, and since then - whether by luck or actually by virtue of the new version - I haven't had any freezing. Just a tip to try disabling extensions, particularly if they have to do with YouTube.

Safari keeps crashing/freezing after install of El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.