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.

El Capitan 10.11.4 Issues Freeze/Fans.

Hello to everyone, to start i apologize in advance for my english since it's not my first language.

I own a new MacBook Pro Retina 13" Early 2015.

Since the last 5 months i had the OSX El Capitan 11.10.3 that came out of the box with the computer. And it worked always perfectly.
In the latest 5 months the mac never gave me any kind of issues!!
I use mostly the computer for listen music, browsing, chatting or writing texts (really basic usage nothing heavy)


Unfortunately i have to say, a couple of days ago on the App Store i noticed a new Update of OSX the "11.10.4" version and i decided to upgrade.
Well after a couple of hours i upgraded to the newer version my mac started to have several issues.
First of all the Fans. Without any kind of reason after 1 or 2 hour after the upgrade (i was simply browsing the web with 2 pages open on safari in specific facebook and youtube)
The fans started to run really crazy and loud for 3/4 minutes... so loud that i thought that the computer was exploding and i closed all the application and waited for the fans to runs slow. To the touch the aluminum of the mac was not hot... Ambient temperature.
This problem happened only the first day i upgraded. But to be honest sometimes i'm experiencing fans that sometimes runs fast and loud without any reason.


Last but absolutely not least.... FREEZING!!! Strangely also this problem showed up the same day i upgraded my macbook pro to the 11.10.4 version and this happened to me about 5 times right now!! and it's becoming a nightmare!!
While using the computer the mac
just simply freeze the screen (mouse is stuck without the wheel is totally freeze) and after 4/5 seconds that the screen is stuck also the haptic vibration of the trackpad stops work. I tried to leave the mac like this for about 10 minute but nothing... only an hard reset can solve this problem..

Last time happened just an hour ago circa and this is why i'm here..


I already tried to boot the computer with CMD+D for Apple Diagnostic and check the hardware, but it's completely fine showing a message "No Issues Found" ADP000.

Looking at the console i saw few messages strange but as i'm not a technician i don't know what kind of problem is...


Anyone of you is experiencing this problems on their macs?

Posted on Mar 25, 2016 7:51 AM

Question marked as Top-ranking reply

Posted on Mar 25, 2016 8:01 AM

First: you ElCapitan, but have made typos in the numbers: 10.11.3 was on it and 10.11.4 is now on it (I make the same typos always).

Your issue may be because of Spotlight indexing, but I am not sure.

I propose to shutdown the mac and

Then start while holding the CMD+R keys: it starts slowly in the so called Recovery Partition. Choose "install OS" from the menu: it will install OSX over what is in the mac, it leaves your user data alone. You need to have a consistent internet connection, because the OS is downloaded again. So it takes time, be prepared for that. After that the mac restarts and installs. Supposedly all "fallen bits" are corrected.

64 replies

Mar 27, 2016 8:11 AM in response to Community User

I have the same issue. At first i thought something is wrong with the hardware, but after checking my system logs I was sure Safari caused the problem. I recorded the exact timing of the incident and managed to locate the log messages. Although, I have not found any solution for the problem.

"MacBook Pro Retina 13-inch 2015"


Here are the messages:

3/26/16 3:52:16.000 PM syslogd[41]: ASL Sender Statistics

3/26/16 3:52:18.604 PM com.apple.xpc.launchd[1]: (com.apple.WebKit.WebContent.E17BADA9-6E18-4576-9902-B4A0FD642070[730]) Service exited with abnormal code: 1

3/26/16 3:52:21.087 PM WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0x179 is not attached to window 0x17a

3/26/16 3:52:21.547 PM Safari[425]: tcp_connection_tls_session_error_callback_imp 115 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

3/26/16 3:52:47.899 PM Safari[425]: tcp_connection_destination_handle_tls_close_notify 110 closing socket due to TLS CLOSE_NOTIFY alert

3/26/16 3:52:47.900 PM Safari[425]: tcp_connection_tls_session_error_callback_imp 110 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

3/26/16 3:54:00.056 PM WindowServer[173]: Surface testing disallowed updates for 10 sequential attempts...

3/26/16 3:54:00.253 PM WindowServer[173]: Surface test allowed updates after 51 attempts (204 ms)

3/26/16 3:59:00.062 PM WindowServer[173]: Surface testing disallowed updates for 10 sequential attempts...

3/26/16 3:59:00.636 PM WindowServer[173]: Surface test allowed updates after 131 attempts (524 ms)

3/26/16 3:59:01.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1459025943

3/26/16 3:59:01.533 PM com.apple.mtmd[201]: Set snapshot time: 2016-03-26 15:59:03 -0500 (current time: 2016-03-26 15:59:01 -0500)

3/26/16 4:00:49.296 PM com.apple.xpc.launchd[1]: (com.apple.WebKit.Networking.6DDEF35E-5FE1-4E8D-83C6-06E4AA2AAB52[743]) Service exited with abnormal code: 1

3/26/16 4:00:52.600 PM GoogleSoftwareUpdateAgent[746]: 2016-03-26 16:00:52.599 GoogleSoftwareUpdateAgent[746/0xa33c2000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x519c40 bundleID=com.google.Keystone.Agent lastCheck=2016-03-26 19:46:51 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/mas/Library/Google/GoogleSoftwareUpdate/TicketStore/Keys tone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>

3/26/16 4:00:53.790 PM com.apple.WebKit.WebContent[742]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 72076 took 0.541573 sec. to complete, 1 reads >= 0.5 sec.

3/26/16 4:00:54.845 PM com.apple.WebKit.WebContent[742]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 20364 bytes @ 31684 took 1.054734 secs. to complete, 1 reads >= 1 sec.

3/26/16 4:00:54.962 PM com.apple.WebKit.WebContent[742]: [16:00:54.961] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:00:54.965 PM com.apple.WebKit.WebContent[742]: [16:00:54.965] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7ff3fb171600) rejecting report of layer being serviced - IQ has not yet begun to update

3/26/16 4:00:57.830 PM com.apple.WebKit.WebContent[742]: [16:00:57.830] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:00:57.861 PM com.apple.WebKit.WebContent[742]: [16:00:57.861] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:00:57.862 PM com.apple.WebKit.WebContent[742]: [16:00:57.862] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:00:57.870 PM com.apple.WebKit.WebContent[742]: [16:00:57.870] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:00:57.870 PM com.apple.WebKit.WebContent[742]: [16:00:57.870] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:00:57.871 PM com.apple.WebKit.WebContent[742]: [16:00:57.870] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:00:57.871 PM com.apple.WebKit.WebContent[742]: [16:00:57.871] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:00:59.816 PM com.apple.WebKit.WebContent[742]: [16:00:59.816] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:00:59.817 PM com.apple.WebKit.WebContent[742]: [16:00:59.817] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7ff3fb836400) rejecting report of layer being serviced - IQ has not yet begun to update

3/26/16 4:01:01.346 PM com.apple.WebKit.WebContent[742]: [16:01:01.346] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:01:01.378 PM com.apple.WebKit.WebContent[742]: [16:01:01.377] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:01:01.380 PM com.apple.WebKit.WebContent[742]: [16:01:01.380] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:01:01.388 PM com.apple.WebKit.WebContent[742]: [16:01:01.388] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:01:01.388 PM com.apple.WebKit.WebContent[742]: [16:01:01.388] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:01:01.388 PM com.apple.WebKit.WebContent[742]: [16:01:01.388] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:01:01.388 PM com.apple.WebKit.WebContent[742]: [16:01:01.388] itemasync_SetProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2306

3/26/16 4:01:04.157 PM com.apple.WebKit.WebContent[742]: [16:01:04.157] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:01:04.159 PM com.apple.WebKit.WebContent[742]: [16:01:04.159] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7ff3fb096600) rejecting report of layer being serviced - IQ has not yet begun to update

3/26/16 4:01:50.796 PM com.apple.WebKit.WebContent[742]: [16:01:50.796] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:01:50.830 PM com.apple.WebKit.WebContent[742]: [16:01:50.830] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

3/26/16 4:01:50.832 PM com.apple.WebKit.WebContent[742]: [16:01:50.832] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

3/26/16 4:01:55.835 PM com.apple.WebKit.WebContent[742]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 5 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?

3/26/16 4:01:58.620 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:02:23.688 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:02:23.000 PM syslogd[41]: ASL Sender Statistics

3/26/16 4:02:38.983 PM Safari[425]: tcp_connection_tls_session_error_callback_imp 117 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

3/26/16 4:02:48.715 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:03:13.761 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:03:38.792 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:04:03.834 PM watchdogd[251]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

3/26/16 4:04:19.000 PM kernel[0]: PM notification timeout (pid 95, hidd)

3/26/16 4:04:19.000 PM kernel[0]: PM notification timeout (pid 742, com.apple.WebKit)

3/26/16 4:04:19.000 PM kernel[0]: PM notification timeout (pid 742, com.apple.WebKit)

3/26/16 4:04:19.722 PM CommCenter[261]: Telling CSI to go low power.

3/26/16 4:04:19.727 PM blued[82]: Can't add anymore advanced matching rule for type: 9 - capacity: 0, remaining: 0

3/26/16 4:04:19.729 PM AirPlayUIAgent[302]: 2016-03-26 04:04:19.729114 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification

3/26/16 4:04:20.861 PM cloudfamilyrestrictionsd[323]: CFRPushManager : connection:didChangeConnectedStatus: : 0

3/26/16 4:04:54.000 PM bootlog[0]: BOOT_TIME 1459026294 0

Mar 28, 2016 3:49 AM in response to maskm

my macbook freeze again today...

check this...


  • 28.03.2016 10:38:45,362 com.apple.WebKit.WebContent[533]: [10:38:45.362] itemasync_CopyProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2092
  • 28.03.2016 10:38:45,362 com.apple.WebKit.WebContent[533]: [10:38:45.362] itemasync_CopyProperty signalled err=-12785 (kFigBaseObjectError_Invalidated) (invalidated) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/Player/FigPlayer_Async.c line 2092
  • 28.03.2016 10:38:45,622 com.apple.WebKit.WebContent[533]: [10:38:45.622] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification
  • 28.03.2016 10:38:50,623 com.apple.WebKit.WebContent[533]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 5 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?
  • 28.03.2016 10:39:00,624 com.apple.WebKit.WebContent[533]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 10 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?
  • 28.03.2016 10:39:07,751 watchdogd[337]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
  • 28.03.2016 10:39:39,000 bootlog[0]: BOOT_TIME 1459150779 0

Mar 31, 2016 7:16 AM in response to maskm

So far as i can see also other users in other forums are experiencing the same issues since the upgrade!!!
This is unbelievable!!! Are passed days since i sent to the apple team an email about this issues and i received ZERO answers from the team and the problem it's still not solved!!! To not mention the apple store personnel that it's totally useless without providing to you any technical solutions/answers!!!

It's really unacceptable spend lot of money on apple products to receive no answers or knowing what's happening to the mac!!


However... today the icing on the cake!!!

My macbook started also to have a weird problem i've never seen at login page!

If i put my mac in "sleep" mode at wake up my mac:
Problem number 1) doesn't ask any password to access (i already check under: "system preferences > privacy and security" and it's set up on "immediately")
Problem number 2) the weird thing is that i see my login avatar and account name in a transparency on the desktop!! But my mac is fully accessible!!!

If i put my mac in sleep mode and someone else wake up by simply stand up the monitor of my macbook pro he can access all my data!!!!! without limitations!!!
This to me looks like a huge bug and security flaw!!! that should be fixed!!!


This happen only in "sleep" mode.. With restart or shut down this problem doesn't happen at all..


Does this problem at login page happen also to you guys?? 😟 I'm so frustrated about this issues!! i start to regret to have updated my mac.....

Mar 31, 2016 11:11 PM in response to my ginger

I have installed Adobe Flash Player, Microsoft Silverlight and Ad Block. This is all i have installed on the safari side.
As i said, i do basic things on this mac so i do not have installed strange third party software, illegal or unidentified.
All the softwares are updated to the latest versions.


I will try a PRAM reset today...

Mar 31, 2016 11:55 PM in response to maskm

More than a solution it looks like an ugly patch.... And to be honest, it's a compromise that i'm not no longer willing to accept it from Apple in general..

Especially after spending over than 2000 euro for a computer. It should run smooth as butter and receive better services.

In almost 15 years of mac i've never seen all the kind of problems i've seen it in the last 5 years...


Apple should stop with this campaign to release almost every year a new OS with a dumb name just to make us believe they are giving to us something "new"...
These psychological tactics can work with children or fanatics...

They should start to think to settle down with a version and improve it!! Just like happened in a distant past...

Apr 1, 2016 11:59 AM in response to Community User

Do you run any other web browsers? And have you installed any plug-gins or extensions for them or safari? Try disabling ad block in safari. You could also delete and then reinstall Adobe Flash Player from the Adobe site. https://helpx.adobe.com/flash-player/kb/uninstall-flash-player-mac-os.html Here is some useful info for safari. http://www.chriswrites.com/20-reasons-safari-crashes/

Apr 1, 2016 1:04 PM in response to Community User

JD1127 wrote:


More than a solution it looks like an ugly patch.... And to be honest, it's a compromise that i'm not no longer willing to accept it from Apple in general..

Especially after spending over than 2000 euro for a computer. It should run smooth as butter and receive better services.

In almost 15 years of mac i've never seen all the kind of problems i've seen it in the last 5 years...


Apple should stop with this campaign to release almost every year a new OS with a dumb name just to make us believe they are giving to us something "new"...
These psychological tactics can work with children or fanatics...

They should start to think to settle down with a version and improve it!! Just like happened in a distant past...

Honestly just had the freeze issue now cleared up -- in Snow Leopard which I have had since it came out. Its not that its the most stable - its just that its too expensive to keep buying hardware and software because Apple drops support.


The underlying problem for the freeze - seems to be a problem between Finder/spotlight indexing getting overwhelmed and taking too much memory when your drives have many changes - and that includes time machine --- and the underlying UNIX system handling of the disks.


Big problem with Apple - is lack of easy access documentation during setup - or update - so you are on your own.


My main reason to update from a power mac to the intel - was a failing hard-drive.


Oh - and another reason for not updating - cannot get the OSX on Media and am in an area where the most stable internet access is slow.

Apr 2, 2016 12:14 AM in response to maskm

I thought that was the case as well but I found that Chrome with Flash also resulted in the whole system freezing up. The issue seems to go back to the a common denominator - the hardware acceleration used by Flash. I've disabled Flash on Chrome which forces websites to serve up HTML5 and the freezes don't occur. I have read though about Safari users who have uninstalled Flash from their system and Safari still results in freezing when using HTML5 videos which makes me wonder whether it has something to do with Safari and how it specifically does video playback given that Chrome invokes a seperate process and uses XPC to communicate with the decoder when doing a video playback rather than using its own built in h264 video decoder.

Apr 6, 2016 12:35 PM in response to Community User

Have you tried accessing the Display settings dialog from within a Flash widget and unchecking 'hardware acceleration' to see if that suppresses the freezes in Safari? I have seen a similar issue in 10.11.4 on a MacPro 3,1 with ATI Radeon HD 2600 XT graphics. In that case I get a GPU Debug from the kernel in the system log after a spin dump in the WindowServer.

El Capitan 10.11.4 Issues Freeze/Fans.

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