[doublepost=1463169673][/doublepost]Uninstall .SAVER screen saver "Aerial.saver", if you have it installed. Decided me.Hello, for more than a month now, ever since I updated to the final 10.11.4 my macbook completely freezes in Safari and other apps at random times, about once a week.
It usually happens when I click on a link, switch tabs, go back one page, etc. The cursor freezes, the screen freezes, the keyboard...it becomes absolutely unresponsive, even the trackpad loses it's force touch and you can't feel the feedback vibration, the only thing that is still responsive is the caps lock light.
It never recovers from the freeze on its own and the only way out is to force shutdown.
If you are able to recover from it after 30sec-1min, you are probably experiencing a different issue than the one we have in this thread so please post that issue here instead.
I don't have any extensions installed in Safari, and flash is disabled.
Update: Looks like this is not an isolated case, it's a system framework or an Intel Graphics driver bug, a lot of people report 10.11.4 freezing especially people with rMBP 13'' 2015.
Please take a moment and report this to http://www.apple.com/feedback/macosx.html and include this thread link so they can see this.
Also, if you are able, post a video when this happens next time to you. I am collecting them and I'll make a compilation once I get enough of them.
Update 2:
Safari Technology Preview Version 1 also freezes.
OS X 10.11.5 beta 1 also freezes.
I just had a freeze in Chrome, plus in Photoshop, therefore I'm joining everyone else who has "The freeze" in other apps.
Here is the moment in the log I believe the crash happened, pay attention to the first 3 lines:
Code:Mar 25 18:53:01 Macbook com.apple.WebKit.WebContent[2172]: [18:53:01.241] 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 Mar 25 18:53:06 Macbook com.apple.WebKit.WebContent[2172]: <<<< 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? Mar 25 18:53:08 Macbook watchdogd[284]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Mar 25 18:53:10 Macbook Safari[509]: tcp_connection_destination_handle_tls_close_notify 572 closing socket due to TLS CLOSE_NOTIFY alert Mar 25 18:53:10 Macbook Safari[509]: tcp_connection_tls_session_error_callback_imp 576 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32 Mar 25 18:53:16 Macbook spindump[2217]: Invalid connection: com.apple.coresymbolicationd Mar 25 18:53:16 Macbook com.apple.WebKit.WebContent[2172]: <<<< 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? Mar 25 18:53:28 Macbook com.apple.usbmuxd[83]: _SendAttachNotification Device cc:20:e8:13:ef:0c@fe80::ce20:e8ff:fe13:ef0c._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification. Mar 25 18:53:41 Macbook CommCenter[242]: Telling CSI to go low power. Mar 25 18:53:41 Macbook AirPlayUIAgent[570]: 2016-03-25 06:53:41.997718 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification Mar 25 18:53:41 Macbook sharingd[297]: 18:53:41.999 : BTLE scanner Powered Off Mar 25 18:53:42 --- last message repeated 1 time ---
I do not have a backup of 10.11.3. I back up all my work files and documents in the cloud. I did not assume that an OS update can break basic internet browsing.
And where can I get an image of 10.11.3? People seem to have them lying around, but with all my searching I do not seem to find anything...
Yeah, it looks like your crash is the same as mine, I can't find "/Library/Caches/com.apple.xbs" so I can't see what's there on line 92.
From my understanding, this is definitely a Safari bug, it happens randomly, every week or so, right after I press on a link (in Safari), not sure if it can be manifested in other browsers since it's the Webkit that crashes, specifically the FigAgglomeratorSetObjectForKey, I see more and more people reporting this so hopefully someone notices it.
Same issue here... Can anyone confirm if I stop using Safari it will not happen again?
(Using MBPr early 2015 and OSX 10.11.4)
Thanks
You gonna ignore the 25-35% of the non 2015 Macs
I don't understand what are you trying to say about the common denominator, the common denominator is the macbook and imacs from 2015 and the specific drivers used for their hardware.1.
"Am not even using the El Capitan update yet.
Nor have changed anything.
Was just about to finally update this morning.
Not aware of what was taking place, I could not get into my email, although i could calendars etc.
Concerned, I changed my password.
It said it was accepted but I still can't get my email and its locked me out of my home network for streaming to the TV etc.
Can still access Netflix but that's it.
Nor will it recognize the new password on either of my cell phones-yet to try two ipads but i know they won't work either.
My email just stopped responding as of sometime overnight.
Also not letting me change the password in my mail settings on mail app on the Mac.
I was able to change it at icloud.com but I can get in to everything but email.
I am on a 27" retina iMAC using Yosemite still at 10.10.5"
2.
"Just to add that I get safari freezing especially when hitting a href. safari 9.1 os 10.11.4 iMac 21.5 late 2012."
3.
I have a 27" iMac bought in the fall of 2011. Since the 10.11.4 update, it has not been randomly freezing, but it often beachballs on awaking from sleep, and I cannot log in without power cycling.
4.
I took my iMac in to the Genius Bar and they told me it was a logic board problem, even though it only occurred once I upgraded 10.11.4. It was crashing almost every 30 minutes. New logic board, and the freezing is not occurring, yet. So, is the issue totally hardware independent? Hard to say.
5.
It's happening to me too and I don't even have multiple graphic cards. I've got a Mac mini late 2012 with Intel hd4000 and I've experienced multiple graphic hangs and black screens. I'm on the latest release of El Capitán since October.
6. My issue is a bit different in that it freezes permanently but restarts on it's own after a minute or so. I also don't have to be watching youtube or whatever, it freezes when I'm not even using it.
"end quote"- he is also reporting the freeze after the latest beta 4 which at least 5 people reported that it was fixed, so not sure what's happening here.
7. Uninstall .SAVER screen saver "Aerial.saver", if you have it installed. Decided me.
8. FWIW I'm getting the crashes and beachballs with a late 2013 Retina MBP 13". It seems like it's tied to certain web content - I haven't had trouble with Youtube videos as others have, but certain news sites (especially the ones that have kind of terrible layout and a lot of annoying ad pop-ups and kind of generally click-bait construction) seem to trigger it more than anything else. In fact I don't think it's ever happened outside of that - none of the sites I routinely use, none of my business applications, Facebook, etc - none of them seem to cause the problem.
9. WOW, running El capitan 10.11.4, never have an issue on MBP (late 2013) 15" 16GB/512.
occasionally safari contextual menu have a slow response, but nothing more.
I know for me, it's easy to tell what's happening on the 2015 model because the Force Touch trackpad shuts down. Oddly though, last time it happened to me, the audio from the video I was watching still played in the background, indicating that while the trackpad and keyboard were not responding, the system was still functioning in SOME capacity. Very strange.
OP here.
I'm going to bite the bullet and announce that 10.11.5 beta 4 has fixed the freeze for me.
I am adding back all my extensions, flash, etc. exactly the way I had it before 10.11.4 to test this further.
After one full week of testing with 12-15 hours a day and lots of youtube videos and exclusively Safari use I haven't had a freeze.
Please read my first post for exact details of this issue.
Seems like a lot of people suggest stuff so I'll chime in:
1. Chrome/Firefox/Opera does not fix the issue, if it does, you weren't affected by this specific issue.
2. If you have an older machine (non-2015) you are most likely not affected by this issue(the insanely lag caused by the hard drive cable failure in the macbook pro 2012 comes to mind).
3. Disabling flash doesn't help.
4. The issue is only affecting 10.11.4, if you had it earlier, it's not the issue discussed in this thread.
The solution right now is to wait for 10.11.5 which should be released in about a month-ish.
If you have a time machine backup use that to downgrade to 10.11.3.
If you want to bite the bullet like me and upgrade to the beta, register to the public beta program. (it's free)
If you don't, but you have decent skills searching google and can spot a good blog from a scam, search for an offline full 10.11.3 installer, if you search through this thread you can find more detailed steps on how to do this, including the expired certificate fix.
No, the common denominator is 10.11.4, not hardware, and there is 1 billion other possible reasons behind these freezes than "specific drivers".I don't understand what are you trying to say about the common denominator, the common denominator is the macbook and imacs from 2015 and the specific drivers used for their hardware.
The problem was introduced in 10.11.4, 10.11.3 had no issue with this kind of freezing, the engineers most likely looked what changed between 10.11.3 and 10.11.4 rather than focused on some arbitrary hardware chosen by you based on nothing other than speculationI'm pretty sure their engineers can spot the issue very quick without the need to test it on 20 different machines from different years and configurations.
Exactly, you are speculating, but make it sound like facts and i´ve seen you many times being stubborn and way to defensive everytime someone else on this forum report the issue on another hardware than your beloved 2015 MBP.I'm just speculating