You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

mac extremely slow (randomly), memory full, CPU fine

Am struggling to troubleshoot what is wrong but Mac performing super slow (occasionally will free up for a min or two). Upgrade to El Capitan - didn't help or hurt. reset PRAM and SMC. Freed up space on HD (23% free). Disk Utility/Onyx run and no issues (except for permissions). Watch Activity Monitor and don't think it is CPU. memory is now full but wasn't always - Kernal_task highest usage (450MB). Disk usage spikes occasionally (but not sure connected to issue). Indexing off. Created a new account to logon; same problem. Any suggestions to troubleshoot would be greatly appreciated.

Posted on Jan 14, 2016 4:56 PM

Reply
20 replies

Jan 14, 2016 5:45 PM in response to scootermanss

Lacking any more info from you, your symptoms sound like problems due to unneeded third-pary software. Do any of the following apply to your computer?:


1) Are you running any anti-virus/internet security applications?

2) Are you running any "cleaning/tune-up/optimization" applications?

3) Any peer-to-peer or torrent downloading software?

4) Any third-party disk backup software that came bundled with an external hard drive?

5) Any online backup scheme other than iCloud (Carbonite; GoogleDrive; MS One Drive)?

6) Did your financial institution ask you to install Trusteer EndPoint Protection (also known as Trusteer Rapport)?


Early in the OSX days, Onyx was a useful tool with some of its functions but others could cause problems if improperly applied. Today, Mac OSX takes very good care of itself and does not need things like Onyx. I don't think I've needed it since upgrading to OS 10.4.

Watch Activity Monitor and don't think it is CPU.


Watching Activity Monitor won't help unles you have its "View" menu set properly. YOu must set the View to "All Processes" or you can miss some very nasty processes misbehaving.


If you are not sure what is installed, please download and install this free utility:


http://www.etresoft.com/etrecheck


It is secure and written by one of our most valued members to allow users to show details of their computer's configuration in Apple Support Communities without revealing any sensitive personal data.


Run the program and click the "Copy report to clipboard" button when it displays the results. Then return here and paste the report into a response to your initial post. It can often show if any harmful files/programs are dragging down your performance.

Jan 14, 2016 6:00 PM in response to scootermanss

When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

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.

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.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages 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 it useless for 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.

When you post the log extract, 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.

Jan 14, 2016 6:54 PM in response to Linc Davis

1/14/16 9:48:12.138 PM WindowServer[132]: CGXDisplayDidWakeNotification [5957761975137]: posting kCGSDisplayDidWake

1/14/16 9:48:12.139 PM WindowServer[132]: handle_will_sleep_auth_and_shield_windows: Deferring.

1/14/16 9:48:12.260 PM identityservicesd[235]: <IMMacNotificationCenterManager: 0x7fbf2941b430>: notification observer: com.apple.iChat notification: __CFNotification 0x7fbf2963b1f0 {name = _NSDoNotDisturbDisabledNotification}

1/14/16 9:48:16.036 PM identityservicesd[235]: <IMMacNotificationCenterManager: 0x7fbf2941b430>: NC Disabled: NO

1/14/16 9:48:16.042 PM identityservicesd[235]: <IMMacNotificationCenterManager: 0x7fbf2941b430>: DND Enabled: NO

1/14/16 9:48:16.042 PM identityservicesd[235]: <IMMacNotificationCenterManager: 0x7fbf2941b430>: Updating enabled: YES (Topics: (

))

1/14/16 9:48:56.122 PM WindowServer[132]: disable_update_timeout: UI updates were forcibly disabled by application "Dock" for over 1.00 seconds. Server has re-enabled them.

1/14/16 9:49:10.123 PM WindowServer[132]: disable_update_likely_unbalanced: UI updates still disabled by application "Dock" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

1/14/16 9:49:34.023 PM WindowServer[132]: common_reenable_update: UI updates were finally reenabled by application "Dock" after 38.90 seconds [0.03fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])

1/14/16 9:49:34.025 PM Dock[194]: void CGSUpdateManager::log() const: conn 0x880b: spurious update.

1/14/16 9:49:36.879 PM WindowServer[132]: disable_update_timeout: UI updates were forcibly disabled by application "Dock" for over 1.00 seconds. Server has re-enabled them.

1/14/16 9:49:39.540 PM WindowServer[132]: common_reenable_update: UI updates were finally reenabled by application "Dock" after 3.66 seconds [0.27fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps])

1/14/16 9:49:53.888 PM lsd[191]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist

1/14/16 9:50:02.879 PM mds[38]: (Server.Warning:445) No stores registered for metascope "kMDQueryScopeComputer"

1/14/16 9:50:03.392 PM Console[520]: assertion failed: 15C50: libxpc.dylib + 63930 [61AB4610-9304-354C-9E9B-D57198AE9866]: 0x89

1/14/16 9:50:04.617 PM com.apple.xpc.launchd[1]: (com.apple.quicklook[531]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook

1/14/16 9:50:33.025 PM QuickLookSatellite[532]: CGSConnectionByID: 0 is not a valid connection ID.

1/14/16 9:50:33.025 PM QuickLookSatellite[532]: Invalid Connection ID 0

1/14/16 9:50:33.243 PM QuickLookSatellite[532]: CGSConnectionByID: 0 is not a valid connection ID.

1/14/16 9:50:33.243 PM QuickLookSatellite[532]: CGSConnectionByID: 0 is not a valid connection ID.

1/14/16 9:50:33.244 PM QuickLookSatellite[532]: CGSConnectionByID: 0 is not a valid connection ID.

1/14/16 9:50:33.246 PM iconservicesagent[237]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fb9b1510fd0>.

Jan 14, 2016 7:20 PM in response to scootermanss

a few more....


1/14/16 10:17:41.541 PM WindowServer[132]: _CGXRemoveWindowFromWindowMovementGroup: window 0x26 is not attached to window 0x39

1/14/16 10:17:41.751 PM Safari[315]: tcp_connection_tls_session_error_callback_imp 62 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

1/14/16 10:17:46.660 PM Safari[315]: tcp_connection_tls_session_error_callback_imp 63 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

1/14/16 10:17:49.924 PM WindowServer[132]: _CGXRemoveWindowFromWindowMovementGroup: window 0x26 is not attached to window 0x39

1/14/16 10:17:50.109 PM Safari[315]: tcp_connection_tls_session_error_callback_imp 71 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

1/14/16 10:19:15.734 PM com.apple.WebKit.Networking[316]: CFNetwork SSLHandshake failed (-9806)

1/14/16 10:19:15.743 PM com.apple.WebKit.Networking[316]: NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9806)

Jan 14, 2016 7:46 PM in response to scootermanss

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.7 ("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 a particular line of text 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 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. If you don't see it within about 15 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. If you close the Terminal window while the test is still running, the partial results won't be saved and you'll have to start over.

11. When the test is complete, or if you stopped it because it was taking too long, 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. 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're told to 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.

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

Jan 15, 2016 7:27 AM in response to scootermanss

A

I have limited information to go on, because an administrator password wasn't entered when you ran the test. If the steps below don't solve the problem, consider running the test again and entering the password.

B

Some of your user files (not system files) have incorrect permissions or are locked. This procedure will unlock those files and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.

Please back up all data before proceeding.

Step 1

If you have more than one user, and the one in question is not an administrator, then go to Step 2.

Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):

sudo find ~ $TMPDIR.. -exec chflags -h nosappnd,noschg,nosunlnk,nouappnd,nouchg {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-

You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.

Step 2 (optional)

Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.

Start up in Recovery mode. You may be prompted to select a language, then the OS X Utilities screen will appear.

If you use FileVault 2, select Disk Utility, then select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another drive icon. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main screen.

Select

Utilities Terminal

from the menu bar. A Terminal window will open. In that window, type this:

resetp

Press the tab key. The partial command you typed will automatically be completed to this:

resetpassword

Press return. A Reset Password window will open. You’re not going to reset a password.

Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.

Select your username from the menu labeled Select the user account if not already selected.

Under Reset Home Directory Permissions and ACLs, click the Reset button.

Select

Restart

from the menu bar.

C

Back up all data.

Run the following command in the same way as before. It moves to the Trash "semaphore" files that have not been cleaned up by the system and may be interfering with normal operation. The files are empty; they contain no data. There will be no output this time.

find L*/{Con*/*/Data/L*/,}Pref* -type f -size 0c -name *.plist.??????? -exec mv {} .Trash/ \; 2>&-

Log out or restart the computer and empty the Trash.

D

Please back up all data before proceeding.

Launch the Font Book application and validate all fonts. You must select the fonts in order to validate them. See the built-in help and this support article for instructions. If Font Book finds any issues, resolve them.

Start up in safe mode to rebuild the font caches. Restart as usual and test.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode. In that case, ask for instructions.

If you still have problems, then from the Font Book menu bar, select

FileRestore Standard Fonts...

You'll be prompted to confirm, and then to enter your administrator login password.

Also note that if you deactivate or remove any built-in fonts, for instance by using a third-party font manager, the system may become unstable.

E

Spotlight indexing has been disabled on the startup volume. If you added the volume to the Privacy list in the Spotlight preference pane, you should remove it. Then please enter the command below in the same way as before:

sudo mdutil -i on /

Below the command you entered, you should see these lines in the Terminal window:

/:
Indexing enabled.

If that's not what you see, please post your results.

Jan 15, 2016 12:14 PM in response to Linc Davis

Linc, executed all of the steps above except for B2 as B1 seemed to work. I reran your script, which can be found here: http://pastebin.com/egjqA89L . My admin did not originally have a password but does now so hopefully your script grabbed everything. Performance thus far is a bit (but still randomly sluggish) and thus am not sure I cleaned up everything. Please let me know your thoughts. Thanks again.

Jan 18, 2016 12:12 PM in response to Linc Davis

Linc, I'm afraid I am still experiencing tremendous sluggishness. Occasionally, it gets better for 5-10 mins but then reverts back to being unbearably slow.

Here are a few recent messages from console. Happy to rerun your script if you that is helpful and you are still willing to help me troubleshoot. thanks.

1/18/16 12:58:57.839 PM iconservicesagent[226]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7f9452d0efb0>.

1/18/16 12:58:57.839 PM quicklookd[268]: Error returned from iconservicesagent: (null)

1/18/16 1:01:04.954 PM Spotlight[191]: Metadata.framework [Error]: mdsCopyStorePaths failed: (268451843) (ipc/rcv) timed out

1/18/16 1:01:25.000 PM kernel[0]: en1: 802.11d country code set to 'US '.

1/18/16 1:01:25.000 PM kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165

1/18/16 1:01:35.030 PM Spotlight[191]: Metadata.framework [Error]: mdsCopyStorePaths failed: (268451843) (ipc/rcv) timed out

1/18/16 1:03:42.357 PM Spotlight[191]: Metadata.framework [Error]: mdsCopyStoreInformation failed: (268451843) (ipc/rcv) timed out

1/18/16 1:05:24.300 PM Spotlight[191]: Hang timer fired; exiting

1/18/16 1:05:24.301 PM SystemUIServer[184]: Spotlight: Service connection interrupted!

1/18/16 1:08:28.000 PM syslogd[21]: ASL Sender Statistics

1/18/16 3:01:12.657 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000003.AppleSpell" tried to hijack endpoint "Multilingual (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:01:17.818 PM Safari[303]: Couldn't contact spell checker for Multilingual

1/18/16 3:01:36.513 PM Safari[303]: tcp_connection_tls_session_error_callback_imp 24 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

1/18/16 3:02:18.252 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000004.AppleSpell" tried to hijack endpoint "da (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:02:18.252 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000004.AppleSpell" tried to hijack endpoint "de (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:02:18.253 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000004.AppleSpell" tried to hijack endpoint "en (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:02:18.253 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000004.AppleSpell" tried to hijack endpoint "en_AU (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:02:18.253 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000004.AppleSpell" tried to hijack endpoint "en_CA (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:05:59.733 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000008.AppleSpell" tried to hijack endpoint "ru (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:05:59.733 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000008.AppleSpell" tried to hijack endpoint "sv (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:05:59.733 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000008.AppleSpell" tried to hijack endpoint "tr (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:05:59.733 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.user.501) Service "com.apple.xpc.launchd.oneshot.0x10000008.AppleSpell" tried to hijack endpoint "Multilingual (Apple)_OpenStep" from owner: com.apple.xpc.launchd.oneshot.0x10000002.AppleSpell

1/18/16 3:06:25.208 PM AppleSpell[348]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid

1/18/16 3:06:25.208 PM AppleSpell[348]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid

1/18/16 3:06:25.208 PM AppleSpell[348]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid

1/18/16 3:06:25.208 PM AppleSpell[348]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid

Jan 19, 2016 4:56 PM in response to scootermanss

This procedure will delete certain temporary and cache files. The files are automatically generated and don't contain any of your data. Occasionally they can become corrupt and cause problems such as yours.

Please back up all data and read this whole message before doing anything. If you use Time Machine to back up and it isn't working, ask for guidance.

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

/var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s

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 a subfolder selected. The subfolder has a long name beginning with "zyx" and ending with "2s". Move that subfolder to the Trash. Don't move any of the other subfolders with similar names. 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.

mac extremely slow (randomly), memory full, CPU fine

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