Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

Safari freezes regularly

Been using El Cap since the day it came out. However, for the last few months, Safari has been become increasingly unstable. It often temporarily freezes and then will unfreeze. Worse still, it will often completely freeze to the point my only option is to turn off the iMac.


I have tried removing all website data. I have repaired permissions. No change. I opened up Console and around the time of my most recent freeze, I saw this message repeated dozens and dozens of times:


executeFetchRequest:error: A fetch request must have an entity


I also have noticed this message as well repeated also quite a bit (but it will come up while my Mac is seaming still functioning):


Warning: accessing obsolete X509Anchors.


Any input is greatly appreciated.

iMac, OS X El Capitan (10.11.3), 3.06 GHz i3; 16GB 1333 MHz

Posted on Mar 17, 2016 10:40 AM

Reply
15 replies

Mar 17, 2016 10:52 AM in response to Jdub_3d

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy the text of a particular web page (not this one) to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

8. Launch the built-in Terminal application in any one of the following ways:

☞ Enter the first few letters of its name ("Terminal") 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.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

Test started

Part 1 of 4 done at: … sec

Part 4 of 4 done at: … sec

The test results are on the Clipboard.

Please close this window.

The intervals between parts won't be exactly equal, but they give a rough indication of progress.

Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

12. When you post the results, 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 software that runs this website. Please post the test results 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.

13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Mar 17, 2016 4:03 PM in response to Jdub_3d

A

Please select the Login Items tab in the Users & Groups pane of System Preferences. Delete any items with "Norton" in the name.

If a login item is grayed out and can't be deleted, click the padlock icon in the lower left corner of the window and enter your login password when prompted. Then try again.

B

You have added, or modified the trust settings of, many certificates in the Keychain Access application. Do you know when and why that was done?

Mar 17, 2016 4:13 PM in response to Linc Davis

Thanks for your reply!


A


While I did notice the Norton listed in the report, it isn't listed in the Login Items. I can't recall loading Norton onto any Mac. But then again, perhaps I did buy it (before I knew better) on my first Mac over a decade ago. Whenever I purchase a new Mac, I have used the provided migration tool from the old to new Mac. I've always wondered if stray files where coming over. As I'm sure the report indicated, this iMac is about 5-6 years old.


B


To the best of my knowledge (which is not perfect), the only time I can recall modifing trust settings on certificates is when I have been prompted by Safari when navigating to a site. Often the pop-up window would come up repeatedly and I would simply select the option allowing Safari to always trust. If there are other changes to trust settings, I can't recall.

Mar 17, 2016 4:43 PM in response to Jdub_3d

A

Please back up all data before proceeding.

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

/Library/Preferences/loginwindow.plist

Right-click or control-click the highlighted line and select

Services Reveal in Finder (or just Reveal)

from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart the computer and empty the Trash.

*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select

Go Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You may not see what you pasted because a line break is included. Press return.

B

You should never change the trust settings of any certificate unless you created it yourself. That's one of the most dangerous things you can do with a computer.

Launch the Keychain Access 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.

In the upper left corner of the window, you should see a list headed Keychains. If not, click the button in the lower left corner that looks like a triangle inside a square.

In the Keychains list, there should be items named System and System Roots. If not, select

File Add Keychain

from the menu bar and add the following items:

/Library/Keychains/System.keychain

/System/Library/Keychains/SystemRootCertificates.keychain

Open the View menu in the menu bar. If one of the items in the menu is

Show Expired Certificates

select it. Otherwise it will show

Hide Expired Certificates

which is what you want.

From the Category list in the lower left corner of the window, select Certificates. Look carefully at the list of certificates in the right side of the window. If any of them has a blue-and-white plus sign or a red "X" in the icon, double-click it. An inspection window will open. Click the disclosure triangle labeled Trust to disclose the trust settings for the certificate. From the menu labeled

Secure Sockets Layer (SSL)

select

no value specified

Close the inspection window. You'll be prompted for your administrator password to update the settings.

Now open the same inspection window again, and select

When using this certificate: Use System Defaults

Save the change in the same way as before.

Revert all the certificates with non-default trust settings. Never again change any of those settings.

Select My Certificates from the Category list. From the list of certificates shown, delete any that are marked with a red X as expired or invalid.

Export all remaining certificates (even if valid), delete them from the keychain, and test. For example, there might be a certificate with a name beginning in "Symantec" or "Verisign."

For instructions, select

Help Keychain Access Help

from the menu bar and search for the term "export" in the help window. Export each certificate as an individual file; don't combine them into one big file.

If there's no change, you can reimport the certificates that you exported in this step (if any) by double-clicking them.

Mar 17, 2016 5:25 PM in response to Linc Davis

Okay... I've done as instructed above. I take it I should now just use my Mac as normal and see if the behavior changes?


Btw, I now see from the certificate list the certificates I changed. They were with a web developer and host (same firm). The sites he built and hosted kept prompting me with the window to trust the certificate when I went to the sites he created. I also now recall the same window would pop up for the email (Mac Mail) he hosted. I terminated my relationship about a year ago due to his websites not functioning as promised. So if it was my changing the trust settings of his certificates that are the problem, I'm not surprised.


Btw #2, my machine did prompt me for access to a keychain after I made the changes noted above. Here's a screen shot below I take that is normal?


User uploaded file

Mar 17, 2016 5:32 PM in response to Jdub_3d

Double-click the line below on this page to select it:

com.apple.scopedbookmarksagent.xpc

Copy the selected text to the Clipboard by pressing the key combination command-C.

Launch the Keychain Access application again.

Click in the search field in the upper right corner of the Keychain Access window and press command-V to paste the text you copied earlier. A password item with the above name should appear in the window. Press delete and confirm when prompted. Quit Keychain Access and see whether the prompts have stopped.

Credit for this observation to ASC member bad_friday.

Mar 18, 2016 1:52 PM in response to Linc Davis

Question: So in doing this, I realize that the list of certificates changes depending on which keychain I select. Yesterday, I performed the above operation when I had the "login" keychain selected. I have five other keychains: "System," "X509Anchors," "Microsoft_Intermediate_Certificates," "Local Items," and "System Roots." Should I perform the instructions on all those keychains, and also export/remove all certificates? That is a lot of certificates, btw. System Roots has 188 items.

Mar 22, 2016 11:46 AM in response to Linc Davis

Well, it looks like I spoke too soon. Last two days have been repeated feezing. Can't figure out why it would suddenly start up again. Freezes occured before and after the installation of the new update to OSX.


I took a look at the Console log at the time it froze. Not sure Linc if you'll be notified of this update since I had previously clicked "solved." But if you do, any thoughts are appreciated. I can copy and paste what I saw on console. Wondering if it is related to the com.apple.WindowServer. Twice now on feezes I've seen that in the Console log.


If you don't get a notification, I'll start up a new thread referencing this one. Thx!

Safari freezes regularly

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