Resolved Macbook Pro 2015 with OSX El Capitan 10.11.4 system wide freeze (Read the details)

[vmachiel]

I have a genius bar appointment today to see if they can do anything; anyone think I should actually go?

Yes, and show them what people have found out in this thread. Hopefully they'll finally pass it to engineering.

 

[danisth]

I have been talking to a Senior Advisor via the chat support and have sent him some info via Capture Data which will be passed on to the engineers, I'll post an update if I hear anything back that's helpful.

 

[andre_g]

Brought my freezing work iMac Retina 5K at the local support and tech assistance point. They checked the machine for possible hardware issues, but expectedly they didn't find anything, so I left it there for further evaluation and stress tests. At this point I doubt they're going to find anything relevant hardware-wise, so I asked them to restore a previous version of OS X, since I wasn't able to do it by myself (couldn't even boot from USB to revert back to Yosemite).

I'm rather disappointed with all of this, but if I had to find a lesson to be learned here, that would be to start making regular backups of my machines.

 

[Grimsy]

Well i think there is not only this problem with the 10.11.4. I get back to 10.11.3 using SuperDuper (please, make a clone before updating your system, it can barely save your life .. Apple is not reliable; it's not the first time they screw an update)
The 10.11.4 is not as smooth as the .3 version, for everything. For those having the freezing problem, the entire system is clearly ****ed up, not only web browsing. Looks like to be a deep deep deeepp framework or driver problem. They will have to work hardfor this one :l

 

[crazyitalian198]

This issue has happened to me a few times since I purchased my early 2015 rMBP 13" this summer. I'm not sure when it began. This happened earlier today to me, so I decided to do some researching of the issue. Upon hearing about Safari as a potential culprit, I closed it. I was playing an .mp4 file in quicktime and while scrubbing, the freezing occurred. It happened exactly like everyone else...screen freezes, keyboard and trackpad are no longer responsive, and the only way to get it back to normal is a powerdown and restart.

I honestly don't use my rMBP that much...I have a crappy lenovo for work. I can only imagine that if I used this computer for work that my life would be a living nightmare. This is totally unacceptable.

What version of OS X are people reverting to where this issue no longer remains? I am seeing reports that 10.11.3 is doing the same thing. Should I go back further until Apple sorts this thing out?

 

[Grimsy]

This issue has happened to me a few times since I purchased my early 2015 rMBP 13" this summer. I'm not sure when it began. This happened earlier today to me, so I decided to do some researching of the issue. Upon hearing about Safari as a potential culprit, I closed it. I was playing an .mp4 file in quicktime and while scrubbing, the freezing occurred. It happened exactly like everyone else...screen freezes, keyboard and trackpad are no longer responsive, and the only way to get it back to normal is a powerdown and restart.

I honestly don't use my rMBP that much...I have a crappy lenovo for work. I can only imagine that if I used this computer for work that my life would be a living nightmare. This is totally unacceptable.

What version of OS X are people reverting to where this issue no longer remains? I am seeing reports that 10.11.3 is doing the same thing. Should I go back further until Apple sorts this thing out?

10.11.3 do not have the frezing issue, no. It can have some, because of an outdated version of flash player (known for freezing with safari, fixed by Adobe), but the issue we are talking about has nothing to do with flash player

Can't do the test with the new developper beta 3 but a buddy just texted me that the freezing bug is still not fixied, apparently.
If it's true, it's official, Apple won't give a **** about it.

 

[dmnc]

Another thing I noticed after reverting to 10.11.3 is that the system is a lot more responsive and animations present less stuttering.
I believe that the culprit here is the gpu driver.

 

[Grimsy]

Another thing I noticed after reverting to 10.11.3 is that the system is a lot more responsive and animations present less stuttering.
I believe that the culprit here is the gpu driver.

High chances, yes.
And the reason why it take a lot a time for a fix, because Apple do not make drivers pour hardware parts, and in that case, it's Intel fault (and 90% Apple's), and Apple has to wait a fix from intel.

 

[Dr. James]

Another thing I noticed after reverting to 10.11.3 is that the system is a lot more responsive and animations present less stuttering.
I believe that the culprit here is the gpu driver.

I agree. The mac has crashed by:

-Starting a Youtube video
-Switching desktops
-Changing a Youtube video's quality
-Opening a Quicktime video

Every single of these things are related to video, specifically, things related directly to the video card. Since they correctly worked on previous OS X versions, the new, updated, GPU driver is to blame.

Now, I just hope Apple has seen this by this point.

 

[got556]

I can't imagine having a workload on a 10.11.4 mac right now. I mean you would have to be saving every few minutes just out of fear of freezing...

 

[mantelvaviz]

In my specific case I noticed no problem with Youtube videos, but a lot of time freeze happened when I was scrolling the Facebook timeline that automatically plays the videos as they appear.

In particular, a moment ago for the first time I notice the freezing 'happening' as it started with a few symptoms such as the scrolling of the Facebook timeline being less responsive. Then I insisted on scrolling and the freeze-of-death happened as usual.

28/04/16 00:19:04,416 WindowServer[199]: _CGXRemoveWindowFromWindowMovementGroup: window 0x45 is not attached to window 0x48
28/04/16 00:19:04,962 com.apple.WebKit.WebContent[390]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 74112 bytes @ 1968 took 0.568738 sec. to complete, 1 reads >= 0.5 sec.
28/04/16 00:19:05,837 com.apple.WebKit.WebContent[390]: [00:19:05.837] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototypes/LegibleOutput/FigAgglomerator.c line 92
28/04/16 00:19:05,840 com.apple.WebKit.WebContent[390]: [00:19:05.840] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fa74b9a8200) rejecting report of layer being serviced - IQ has not yet begun to update
28/04/16 00:19:08,864 com.apple.WebKit.WebContent[390]: [00:19:08.864] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototypes/LegibleOutput/FigAgglomerator.c line 92
28/04/16 00:19:08,867 com.apple.WebKit.WebContent[390]: [00:19:08.866] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fa74b070a00) rejecting report of layer being serviced - IQ has not yet begun to update
28/04/16 00:19:28,291 com.apple.WebKit.WebContent[390]: 00:19:28.290 ERROR:    177: timed out after 15.000s (0 0); mMajorChangePending=0
28/04/16 00:19:28,291 com.apple.WebKit.WebContent[390]: [00:19:28.291] faqrp_startTimebaseAndAudioQueue signalled err=-66681 (err) (FigAudioQueueStart(now) failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototypes/RenderPipelines/FigAudioQueueRenderPipeline.c line 1231
28/04/16 00:19:28,292 com.apple.WebKit.WebContent[390]: [00:19:28.292] <<<< Boss >>>> bossSetPossiblyOutsourcedTimebaseRate: FigRenderPipelineSetRate on pipeline 0x7fa74c176890 with timebase rate 1.000 and pipeline rate 1.000, failed with err=-66681
28/04/16 00:19:45,338 com.apple.WebKit.WebContent[390]: 00:19:45.337 ERROR:    177: timed out after 15.000s (0 0); mMajorChangePending=0
28/04/16 00:19:45,338 com.apple.WebKit.WebContent[390]: [00:19:45.338] faqrp_startTimebaseAndAudioQueue signalled err=-66681 (err) (FigAudioQueueStart(now) failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototypes/RenderPipelines/FigAudioQueueRenderPipeline.c line 1231
28/04/16 00:19:45,338 com.apple.WebKit.WebContent[390]: [00:19:45.338] <<<< Boss >>>> bossSetPossiblyOutsourcedTimebaseRate: FigRenderPipelineSetRate on pipeline 0x7fa74c2a54e0 with timebase rate 1.000 and pipeline rate 1.000, failed with err=-66681
28/04/16 00:19:45,378 com.apple.WebKit.WebContent[390]: [00:19:45.378] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification
28/04/16 00:19:45,470 com.apple.WebKit.WebContent[390]: [00:19:45.470] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

 

[JP08]

It happened to me once a few weeks back and hadn't experienced since then until today. But today there was a weird issue with iTunes before it struck. No song would play instead it would just cycle through a playlist I was currently listening too super fast, not even playing any it skipped to.

Then it locked up the whole mac. I wasn't even watching Youtube like the first time, which I thought was the culprit. I guess not.

 

[got556]

...And another one...

 

[akkers]

Last night the freeze happened with i was using split view with Apple Mail and Word side by side. I clicked the email address i added to make sure it was correct and beachball!
Then the window froze, both mail and word became unresponsive. Finally after about 40 seconds i could go back to main desktop but when i tried to shut down the Mac, it did nothing. Finally after waiting for 3-4 mins i hard shutdown the mac.

 

[got556]

Just froze again while having three tabs open in Safari, two of them were Facebook. Closed one of the Facebook tabs and it completely froze. Time to start downgrading to 10.11.3 me thinks. That build was solid for me.

 

[Dr. James]

Time to start downgrading to 10.11.3 me thinks.

I wish I could do the same.

Oh, lovely Apple, look at all the affected users, and look at yourself doing NOTHING to solve this.

 

[dlkolegaev]

This is so annoying, I am studying for finals and this is happening almost every single day! I was planning to make a Genius Bar appointment before I discovered this thread.

This is completely unacceptable, Apple please fix this ASAP!!

 

[dmnc]

I wish I could do the same.

Oh, lovely Apple, look at all the affected users, and look at yourself doing NOTHING to solve this.

I tried to install 10.11.3 from an USB, but it get stuck in "one second remaining" for a lot of time and never finishing. Oh well...Luckily I had a TM backup just from the day before upgrading to 10.11.4.

EDIT: I have a backup of the 10.11.3 installer in an external HDD, maybe it can't be installed because it isn't signed anymore or something?

 

[Dr. James]

I was planning to make a Genius Bar appointment before I discovered this thread.

I suggest you to still go, so they become more aware of this problem.

 

[kjor76]

Hi all, just chiming in. Bought my rMBP 13" about 3 weeks ago as a refurb unit. Wonderful machine apart from choppy graphics when sliding between spaces and of course the freezing up. It happened once or twice last week and daily this week. Very frustrating. Hard to defend apple against PC counterparts when this is happening; it's a work machine and it has frozen during meetings multiple times now. I guess one benefit of the blazing fast SSD is a quick reboot! Here is my console from the latest crash. I was streaming live CNN news on my TV providers website (Horizon Go from UPC in Ireland). Sure hope there is a patch/ fix soon!

28/04/2016 06:25:42.865 com.apple.WebKit.WebContent[2748]: [06:25:42.865] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

28/04/2016 06:25:47.866 com.apple.WebKit.WebContent[2748]: <<<< 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/04/2016 06:25:57.868 com.apple.WebKit.WebContent[2748]: <<<< 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/04/2016 06:26:02.064 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:26:03.071 watchdogd[240]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)

28/04/2016 06:26:17.869 com.apple.WebKit.WebContent[2748]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 20 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?

28/04/2016 06:26:24.008 Safari[2454]: tcp_connection_tls_session_error_callback_imp 44 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

28/04/2016 06:26:27.178 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:26:28.180 watchdogd[240]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)

28/04/2016 06:26:52.323 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:26:53.329 watchdogd[240]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)

28/04/2016 06:26:57.872 com.apple.WebKit.WebContent[2748]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 40 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?

28/04/2016 06:27:17.471 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:27:42.619 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:28:07.767 watchdogd[240]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

28/04/2016 06:28:17.874 com.apple.WebKit.WebContent[2748]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 80 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?

28/04/2016 06:28:58.000 bootlog[0]: BOOT_TIME 1461821338 0

28/04/2016 06:28:59.000 syslogd[42]: Configuration Notice:
ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.

28/04/2016 06:28:59.000 syslogd[42]: Configuration Notice:
ASL Module "com.apple.Accounts" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.

 

[Romf]

A new preview of Safari is available, but didn't see anything about this problem in the changelog file - anyone tried?

 

[JesperA]

A new preview of Safari is available, but didn't see anything about this problem in the changelog file - anyone tried?

I used the first STP for several weeks on 10.11.4 and had no freeze whatsoever, on regular Safari i got freezes several times per day, however, on 10.11.5 PB2 and the new STP i started to get daily freezes on STP too, seems Apple is going backwards on this issue....

 

[mantelvaviz]

Do you think it's possible to avoid the freezing issue using Chrome or Firefox, instead of Safari, or any other browser that may not rely on WebKit, as this may be the main problem highlighted from any error message that appear in Console during the freezing? Or every browser for MacOS use WebKit technology in the background?

 

[dmnc]

A new preview of Safari is available, but didn't see anything about this problem in the changelog file - anyone tried?

This problem is not entirely related to Safari. It's more of a GPU driver issue that's triggered in some circumstances by Safari, in other occasion by QuickTime videos, switching between work spaces, etc. It's really fairly erratic, because it's not consistent, i. e., it doesn't happen always when performing a certain task. Maybe the random nature of the problem is what makes it difficult to solve?

 

[Yokara Karaoke]

I use macbook pro mid 2012, 10.11.4 is pretty good