-
All replies
-
Helpful answers
-
Oct 19, 2015 9:01 PM in response to sbriscoe94by John Galt,Back up your Mac if you have not done so already. To learn how to do that read https://www.apple.com/support/backup/. To learn how to use Time Machine read Use Time Machine to back up or restore your Mac.
If your Mac is momentarily unresponsive, consider the following.
Launch the Console app - it is in your Utilities folder. You can find it by selecting Utilities from the Finder's Go menu.
If the log list column on the left is not already displayed, show the log list by selecting Show Log List from Console's View menu. Select Show Toolbar if it is not already shown.
Locate system.log in the list and select it. Many date and time-stamped entries will appear, hundreds of them, and you must find the entries relevant to your Mac's problem.
To do that click the Clear Display button in the Toolbar. All previously displayed log entries will be disappear.
Next: Perform whatever actions cause the Mac to exhibit the slow behavior. If the problem is caused by errors logged by the system, the Console window will show them being recorded in system.log.
One or more of them, along with their time stamps, may reveal the reason for the problem you describe.
Copy and paste those log entries in a reply. If hundreds of the same repetitive messages appear, please edit them before posting. There should be no need for more than a few log entries.
Most of the entries will be cryptic but will contain information you might consider personal such as your Mac's name. If you do not want that information to appear, delete or obscure it when posting your reply. Leave enough information so that the entries can be deciphered.
-
Oct 19, 2015 10:33 PM in response to John Galtby sbriscoe94,I was not sure how much you would need, so here are some log entries when my computer sounded like it was overworking. Thank you.
Oct 19 22:29:15 unknown iconservicesagent[315]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7ffdca522ef0>.
Oct 19 22:29:15 unknown quicklookd[316]: Error returned from iconservicesagent: (null)
Oct 19 22:29:19 unknown WindowServer[169]: disable_update_timeout: UI updates were forcibly disabled by application "Microsoft Word" for over 1.00 seconds. Server has re-enabled them.
Oct 19 22:29:20 unknown WindowServer[169]: common_reenable_update: UI updates were finally reenabled by application "Microsoft Word" after 1.24 seconds [0.81fps] (server forcibly re-enabled them after 1.02 seconds [1.00fps])
Oct 19 22:29:24 unknown WindowServer[169]: disable_update_timeout: UI updates were forcibly disabled by application "Microsoft Word" for over 1.00 seconds. Server has re-enabled them.
Oct 19 22:29:25 unknown WindowServer[169]: common_reenable_update: UI updates were finally reenabled by application "Microsoft Word" after 1.08 seconds [0.93fps] (server forcibly re-enabled them after 1.01 seconds [1.00fps])
Oct 19 22:29:42 unknown WindowServer[169]: _CGXRemoveWindowFromWindowMovementGroup: window 0x56 is not attached to window 0x133
Oct 19 22:29:52 unknown spindump[408]: Saved spin report for Microsoft Word version 14.5.4 (14.5.4) to /Library/Logs/DiagnosticReports/Microsoft Word_2015-10-19-222952_**-MacBook-Pro.spin
Oct 19 22:29:53 unknown iconservicesagent[315]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7ffdca4100a0>.
Oct 19 22:29:53 unknown quicklookd[316]: Error returned from iconservicesagent: (null)
-
Oct 20, 2015 4:48 AM in response to sbriscoe94by John Galt,Assuming the performance problems are isolated to Microsoft Office, install this update: https://support.microsoft.com/kb/3098229
-
Oct 20, 2015 12:35 PM in response to John Galtby John Galt,Actually, I found a newer one:
http://www.microsoft.com/en-us/download/details.aspx?id=49436
For all I know they may issue another update tomorrow, so you will have to keep on top of these things. Their constant need for maintenance is one of many reasons I no longer use any Microsoft products.
-
Oct 24, 2015 11:33 AM in response to John Galtby sbriscoe94,I am still having the same issue. And it has nothing to do with microsoft.
Oct 24 11:28:35 unknown Safari[1580]: tcp_connection_tls_session_error_callback_imp 432 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22
Oct 24 11:28:39 unknown com.apple.xpc.launchd[1] (com.apple.WebKit.WebContent.0F344604-EDF0-4179-A971-B607069E1D20[2646]): Service exited with abnormal code: 1
Oct 24 11:28:44 unknown WindowServer[173]: send_datagram_available_ping: pid 309 failed to act on a ping it dequeued before timing out.
Oct 24 11:28:49 unknown WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0xba4 is not attached to window 0xba5
Oct 24 11:29:10 --- last message repeated 1 time ---
Oct 24 11:29:10 unknown syslogd[42]: ASL Sender Statistics
Oct 24 11:29:12 unknown WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0xba4 is not attached to window 0xba5
Oct 24 11:29:13 unknown WindowServer[173]: send_datagram_available_ping: pid 309 failed to act on a ping it dequeued before timing out.
Oct 24 11:29:15 unknown WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0xba4 is not attached to window 0xba5
Oct 24 11:29:39 --- last message repeated 2 times ---
Oct 24 11:29:38 unknown WindowServer[173]: send_datagram_available_ping: pid 309 failed to act on a ping it dequeued before timing out.
Oct 24 11:29:59 --- last message repeated 1 time ---
Oct 24 11:29:59 unknown WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0xba4 is not attached to window 0xbe4
Oct 24 11:30:18 --- last message repeated 1 time ---
Oct 24 11:30:18 unknown WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0xba4 is not attached to window 0xba5
Oct 24 11:30:21 unknown WindowServer[173]: send_datagram_available_ping: pid 309 failed to act on a ping it dequeued before timing out.
-
Oct 24, 2015 12:01 PM in response to sbriscoe94by Seanachai,The latest update to El Capitan is 10.11.1, which was released on Oct. 21. It's supposed to address the issues with Office. Try updating to the latest version and post your results.
About the OS X El Capitan v10.11.1 Update - Apple Support
-
Oct 24, 2015 1:24 PM in response to sbriscoe94by tubeswell,★HelpfulI recently had this problem with my mid 2012 Macbook Pro. Tried all the usual reboots and resets and recovery/repairs suggested here, but it kept giving me grief. I finally took it to an Apple repair technician who diagnosed a faulty HD cable. He said it was a common problem with these computers. He fixed it with a new improved cable within 24 hours and its just like new. Not saying that's your problem but chances are...