Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The Safari freeze issue, lets fix this
- Thread starter JesperA
- Start date
- Sort by reaction score
I got a call from apples engineering team today, they want me to do some diagnostics when it freezes so they can come up with a fix.
Please keep us posted on how this all works out. I'm so fed up with this issue. Using STP as a workaround and hoping for the best. But seriously, it's been long enough. Apple needs to acknowledge this and get a fix out there.
I have an early '08 MBP and my experience with El Cap (10.11.4) is the opposite. I get a 2 second freeze about every 3 seconds when scrolling through Safari but also it seems to be system wide as well. It is always associated with a log error that indicates something about "IOSUSB" and the trackpad. I don't see this error on a 2011 MBA or my 2009 Mac Pro with magic trackpad.
This is cool.
Since I upgraded my 2009 iMac to an SSD Hard drive I have been experiencing this weird crash. (Mouse moves, music plays, Skype works, FTP still uploads and downloads even, but I just can't click. Only after finding this thread did I discover that it is related to Safari, and now it makes sense to me.
Apple Peeps: This problem happens several times a day at least, while in Safari, and actually while SCROLLING.
It doesn't happen all the time, but every time it does, I am scrolling. It can be on Facebook, or this forum, or google, it doesn't matter. Scrolling in Safari = crash.
I will try using only Google for the next few days and see if the problem persists.
Since I upgraded my 2009 iMac to an SSD Hard drive I have been experiencing this weird crash. (Mouse moves, music plays, Skype works, FTP still uploads and downloads even, but I just can't click. Only after finding this thread did I discover that it is related to Safari, and now it makes sense to me.
Apple Peeps: This problem happens several times a day at least, while in Safari, and actually while SCROLLING.
It doesn't happen all the time, but every time it does, I am scrolling. It can be on Facebook, or this forum, or google, it doesn't matter. Scrolling in Safari = crash.
I will try using only Google for the next few days and see if the problem persists.
I just had my first crash after a few days using STP instead of regular safari. So for me, using STP didn't fix the issue. Moving to firefox until a fix is in but not crazy about it.
Noise is getting made. There's an incredibly long thread about this issue going on over at Apple's support forums.
https://discussions.apple.com/thread/7282867?start=0&tstart=0
Now while that's user to user just like here, I can't imagine Apple at this point is totally blind to what's going on. They're just going to keep quiet on it until one day (hopefully soon) it's fixed via an update. But I do think Apple needs to be prodded along on this.
Some people in that discussion are speculating its hardware based. Since this started with with the last few updates for me, I tend to disagree with that assessment.
My 2012 Mac mini is running like my old PowerBook 5300 from 1996 with all the crashes. This just can't continue. I'm going to place a call to Apple tomorrow and see if they can escalate this to their higher level support.
I think all of us should call support and point out the numerous discussions across various sites on this matter as we try and get our specific problems resolved.
My screen froze 3 times last night. I just turned the computer off and left it after it happened the last time. I think I'll be giving Apple a call soon.
Has happened to me twice in about 2 weeks as well, normally with video (HTML5 I think as I removed flash (See here how doing this has at least restored Safari performance to normal for me)).
An apple engineer remoted into my Mac and grabbed a bunch of log files. He also had me do a sys diagnose every time the freeze happens. He gave them to his team. Will report back with any updates.
Yeah, i have done that 10-15 times since Februari but evidently that was not much help for Apple, but yeah, its good that more people do it so hopefully this gets fixed this year.
Happy to report that the latest release of STP has solved this problem for me. Still some quirks but the system isn't locking up.
Ok, i cant believe how bad Apple have handled this, lets recap (this will probably be a wall of text so, yeah)
In the beginning of January Apple release the first dev and pubic betas of 10.11.4, no freeze issues seems to have been reported on this beta
Two weeks later, 25th of Januari i think, Apple released the second beta and if i remember correctly this is where the freeze issues started, i noticed it first on my iMac 2009 and a couple of days later on my 15" rMBP 2015, i updated to the beta on both hardware because i wanted to make sure all my apps and extensions worked on 10.11.4 betas before Apple released the GA. After several days of my Macs freezing during use in Safari i started to file bug reports to Apple, including sysdiag and crash reports.
When the third beta in the beginning of February did not fix this issue i wrote about the issue on Apples developer forum. That thread got deleted and i got a message from an admin saying that the betas was under NDA and should not be spoken about on a semi-public forum. I know about the NDA on developer betas but was surprised that the admin told me the NDA also applied to the public betas, i thought it cant be right, what would the point of a public beta be then if the community cant report on a major bug, sure we can still file bug reports to Apple but how could we possible figure out if it was a widespread bug or just a bug that only affected one or a couple of individuals. Apple(!), don't throw NDA on public betas AND tell all your community admins to not delete bug report threads. Technically i was not allowed to even make this thread because 10.11.4 was still in beta when i created it, thats insane. A developer beta i can understand the NDA and TOS but on the Public Betas Apple should really free up the terms. I wasn't even allowed to take about it on Apples own developer forum without my threads getting deleted.
I think i created this thread just before PB4 was released because i was fed up with the frequent freezes and Apples poorly management of the threads discussing this issue. At this point i had filed maybe 10 bug reports and feedbacks to Apple, i talked to several "community managers" about this issue and how incredible locked Apple discussion about beta bugs and issues are, it fell on deaf ears though, every level, every stage and every instance i was in touch with Apple the only respons one can get is "We have received your request and will forward it.........", every human at Apple felt like a robot, seems like they have been through a rigorous seminar at Apple on how to interact with customers, developers and community members. Every respons i got might just aswell have been a bot.
I still wanted to know if this was a widespread issue on the betas and if someone else have had this issue but there was no way of knowing since Apple deleted every single thread people created about this issue so none of us that was affected by this could discuss the issue, if there was a fix it would be impossible to know since most of the threads got deleted before even reaching 2-3 replies and those threads that Apple didn't bother to remove did basically not say anything.
What frustrated me the most, i spent 2 month with this issue, in middle-late February the reports started to come in about the issue on non Apple owned forums and other sites, several reported about the issue here on MacRumors in the El Capitan bug report thread, Apple started to allow threads about it on their community forum and the issue started to look even more widespread for each passing day, this was in late February, over 1 month before the GA version, but still, there was NO effective way to interact with Apple and the "community manager" and everyone else on Apples support side seemed to have no intention or did not take this issue seriously, one time when i spoke with a developer manager his attitude was VERY frustrating, when i tried to tell Apple to take this issue serious the response i´ve got every single time was basically "Yeah, it is a beta release, ofcourse it has some bugs, it even tell you to expect them in FAQ", i wanted to scream at them "OFCOURSE i know and expect bugs in the beta releases, thats why i am reporting the bugs, so you can fix them before the GA releases........" but no, no human i spoke to at Apple cared, they basically blocked this issue, i wouldn't even be surprised if the developers didn't even get the reports or even a ticket about the issue when all the manager had that poor attitude to bug reports, and such a serious bug report nonetheless...
For a month, from late February to middle of Mars i did my best to try to get Apple to understand, at this point (middle of Mars), every response i got was "Re-install El Capitan", "Reset PRAM/NVRAM", "Replace the logic bord", they did want to understand that this issue started for all of that had this freeze, it started with 10.11.4, when dual booting my iMac back to 10.11.3 the freeze issue was gone, it was a bug in 10.11.4 but no, Apple refused to take it seriously.
My horror when Apple released 10.11.4 to the public even though the support forum now was filled with reports from people having the freeze issue on the previous betas. 10.11.4 SHOULD NEVER HAVE BEEN RELEASED, over 6, i repeat: 6 betas hade this freeze issue.
So, the upcomming days after the release of 10.11.4 to the public, Apples discussion forum literally exploded with non-beta users getting the very same freeze bug that us beta testers had reported on for 2 month, seriously, 2 month and Apple still release 10.11.4 without even addressing the bug or even accepting that the bug was there. Twitter exploded too, both normal Twitter posts and Twitter posts targeted at Apples Twitter support account was now filled with people experiencing the freeze issue.
This is incredible annoying and frustrating, there seems to be a huge internal wall at Apple, it seems like the developers at Apple is locked into a bunker without any access to the outside world an no bug reports is reaching them. They dont seem to have a system to block a release of OS X if the community is reporting serious and critical bugs, OS X gets released anyway AND Apple actively blocked and removed all the discussions in January and February on their own developer forum so if someone would look at the forum there would be know evidence at all about a critical bug and since the "community manager" and "feedback managers" (humans) had that stupid attitude to this critical bug report they really blocked this issue from really reaching the developers. The issue did not look widespread at all at a first glance in the forums but since the release of the GA and we now are allowed to speak about the release without it having a NDA or TOS, now the issue looks more widespread than anyone of us on the developer beta could have imagined in January.
Apple missed a critical bug, they release an OS X version with a critical bug to the public without listening to us non-Apple developers, now the bug is affecting alot of people, hurting the Apple brand, making devices basically useless, especially in a professional environment, Twitter and Apple forum is now filled with people reporting this issue, as i said before, 10.11.4 should never, EVER have been released.
The communication between beta testers and Apple is HORRIBLE, for such a huge company that is insane how bad the communication and discussion between Apple and beta users and developers are.
Whats the point of Apple even having the PB program when the PB users arent even allowed to take about critical bugs in their own developer forum AND Apple ignore those PB users reports to and release a broken OS X version anyway.
There is alot more to say about Apples handling about this, i didn't really have time to really explain the respons from Apple and the fixes Apple should make, especially to the PB program, i need to go but i can explain some of the stuff better when i come back.
So, the bug seems so be fixed for alot of the devs and PB users in 10.11.5 PB4 BUT that is not released to the public, so basically this issue have existed from January to May, about 4 month, such a critical bug CANT be allowed to exist for so long, Apple really need to change the way they are handling reports and how the community managers handles the interactions between Apple and us.
In the beginning of January Apple release the first dev and pubic betas of 10.11.4, no freeze issues seems to have been reported on this beta
Two weeks later, 25th of Januari i think, Apple released the second beta and if i remember correctly this is where the freeze issues started, i noticed it first on my iMac 2009 and a couple of days later on my 15" rMBP 2015, i updated to the beta on both hardware because i wanted to make sure all my apps and extensions worked on 10.11.4 betas before Apple released the GA. After several days of my Macs freezing during use in Safari i started to file bug reports to Apple, including sysdiag and crash reports.
When the third beta in the beginning of February did not fix this issue i wrote about the issue on Apples developer forum. That thread got deleted and i got a message from an admin saying that the betas was under NDA and should not be spoken about on a semi-public forum. I know about the NDA on developer betas but was surprised that the admin told me the NDA also applied to the public betas, i thought it cant be right, what would the point of a public beta be then if the community cant report on a major bug, sure we can still file bug reports to Apple but how could we possible figure out if it was a widespread bug or just a bug that only affected one or a couple of individuals. Apple(!), don't throw NDA on public betas AND tell all your community admins to not delete bug report threads. Technically i was not allowed to even make this thread because 10.11.4 was still in beta when i created it, thats insane. A developer beta i can understand the NDA and TOS but on the Public Betas Apple should really free up the terms. I wasn't even allowed to take about it on Apples own developer forum without my threads getting deleted.
I think i created this thread just before PB4 was released because i was fed up with the frequent freezes and Apples poorly management of the threads discussing this issue. At this point i had filed maybe 10 bug reports and feedbacks to Apple, i talked to several "community managers" about this issue and how incredible locked Apple discussion about beta bugs and issues are, it fell on deaf ears though, every level, every stage and every instance i was in touch with Apple the only respons one can get is "We have received your request and will forward it.........", every human at Apple felt like a robot, seems like they have been through a rigorous seminar at Apple on how to interact with customers, developers and community members. Every respons i got might just aswell have been a bot.
I still wanted to know if this was a widespread issue on the betas and if someone else have had this issue but there was no way of knowing since Apple deleted every single thread people created about this issue so none of us that was affected by this could discuss the issue, if there was a fix it would be impossible to know since most of the threads got deleted before even reaching 2-3 replies and those threads that Apple didn't bother to remove did basically not say anything.
What frustrated me the most, i spent 2 month with this issue, in middle-late February the reports started to come in about the issue on non Apple owned forums and other sites, several reported about the issue here on MacRumors in the El Capitan bug report thread, Apple started to allow threads about it on their community forum and the issue started to look even more widespread for each passing day, this was in late February, over 1 month before the GA version, but still, there was NO effective way to interact with Apple and the "community manager" and everyone else on Apples support side seemed to have no intention or did not take this issue seriously, one time when i spoke with a developer manager his attitude was VERY frustrating, when i tried to tell Apple to take this issue serious the response i´ve got every single time was basically "Yeah, it is a beta release, ofcourse it has some bugs, it even tell you to expect them in FAQ", i wanted to scream at them "OFCOURSE i know and expect bugs in the beta releases, thats why i am reporting the bugs, so you can fix them before the GA releases........" but no, no human i spoke to at Apple cared, they basically blocked this issue, i wouldn't even be surprised if the developers didn't even get the reports or even a ticket about the issue when all the manager had that poor attitude to bug reports, and such a serious bug report nonetheless...
For a month, from late February to middle of Mars i did my best to try to get Apple to understand, at this point (middle of Mars), every response i got was "Re-install El Capitan", "Reset PRAM/NVRAM", "Replace the logic bord", they did want to understand that this issue started for all of that had this freeze, it started with 10.11.4, when dual booting my iMac back to 10.11.3 the freeze issue was gone, it was a bug in 10.11.4 but no, Apple refused to take it seriously.
My horror when Apple released 10.11.4 to the public even though the support forum now was filled with reports from people having the freeze issue on the previous betas. 10.11.4 SHOULD NEVER HAVE BEEN RELEASED, over 6, i repeat: 6 betas hade this freeze issue.
So, the upcomming days after the release of 10.11.4 to the public, Apples discussion forum literally exploded with non-beta users getting the very same freeze bug that us beta testers had reported on for 2 month, seriously, 2 month and Apple still release 10.11.4 without even addressing the bug or even accepting that the bug was there. Twitter exploded too, both normal Twitter posts and Twitter posts targeted at Apples Twitter support account was now filled with people experiencing the freeze issue.
This is incredible annoying and frustrating, there seems to be a huge internal wall at Apple, it seems like the developers at Apple is locked into a bunker without any access to the outside world an no bug reports is reaching them. They dont seem to have a system to block a release of OS X if the community is reporting serious and critical bugs, OS X gets released anyway AND Apple actively blocked and removed all the discussions in January and February on their own developer forum so if someone would look at the forum there would be know evidence at all about a critical bug and since the "community manager" and "feedback managers" (humans) had that stupid attitude to this critical bug report they really blocked this issue from really reaching the developers. The issue did not look widespread at all at a first glance in the forums but since the release of the GA and we now are allowed to speak about the release without it having a NDA or TOS, now the issue looks more widespread than anyone of us on the developer beta could have imagined in January.
Apple missed a critical bug, they release an OS X version with a critical bug to the public without listening to us non-Apple developers, now the bug is affecting alot of people, hurting the Apple brand, making devices basically useless, especially in a professional environment, Twitter and Apple forum is now filled with people reporting this issue, as i said before, 10.11.4 should never, EVER have been released.
The communication between beta testers and Apple is HORRIBLE, for such a huge company that is insane how bad the communication and discussion between Apple and beta users and developers are.
Whats the point of Apple even having the PB program when the PB users arent even allowed to take about critical bugs in their own developer forum AND Apple ignore those PB users reports to and release a broken OS X version anyway.
There is alot more to say about Apples handling about this, i didn't really have time to really explain the respons from Apple and the fixes Apple should make, especially to the PB program, i need to go but i can explain some of the stuff better when i come back.
So, the bug seems so be fixed for alot of the devs and PB users in 10.11.5 PB4 BUT that is not released to the public, so basically this issue have existed from January to May, about 4 month, such a critical bug CANT be allowed to exist for so long, Apple really need to change the way they are handling reports and how the community managers handles the interactions between Apple and us.
I love Apple, i was running 10.11.5 PB4 for over 2 weeks, it was crazy stable, not a single freeze, updated to 10.11.5 GA today, 3 hours later i got my first freeze while scrolling on Instagram, this makes me miss Windows ME, much more stable.......................
I'm having this issue as well and have for the past couple of months. My 2011 27" hadn't locked up in a couple of weeks, but sure as **** after upgrading ElCap last night it froze. I'm running iStat and notice when this does happen my CPU is running 100%.
Sometimes it will unfreeze, but more often than not I have to power it off and back on. Guess I'll try STP or Chrome and see if this reduces the freezing. Sucks.
Sometimes it will unfreeze, but more often than not I have to power it off and back on. Guess I'll try STP or Chrome and see if this reduces the freezing. Sucks.
Updated last night so today I tried using Safari again and I just had a crash. It might be for a different reason but it seems a bit coincidental. here is the crash log:
Code:
5/17/16 1:58:43.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2300 [IMRemoteURLConne]
5/17/16 1:58:44.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2250 [nsurlstoraged]
5/17/16 1:58:45.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2303 [com.apple.Safari]
5/17/16 1:58:46.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2311 [spindump]
5/17/16 1:58:47.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2312 [spindump_agent]
5/17/16 1:58:48.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2309 [MTLCompilerServi]
5/17/16 1:58:49.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2269 [CalNCService]
5/17/16 1:58:50.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2230 [soagent]
5/17/16 1:58:50.723 PM com.apple.dock.extra[608]: SOHelperCenter main connection interrupted
5/17/16 1:58:50.725 PM Messages[596]: SOHelperCenter main connection interrupted
5/17/16 1:58:51.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2223 [com.apple.Addres]
5/17/16 1:58:52.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2227 [com.apple.InputM]
5/17/16 1:58:53.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2283 [com.apple.Commer]
5/17/16 1:58:54.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2310 [VTDecoderXPCServ]
5/17/16 1:58:55.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2243 [sysmond]
5/17/16 1:58:56.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2231 [WirelessRadioMan]
5/17/16 1:58:56.756 PM CommCenter[299]: Connection interrupted!
5/17/16 1:58:57.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2228 [bird]
5/17/16 1:58:58.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2279 [pbs]
5/17/16 1:58:59.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2248 [pkd]
5/17/16 1:58:59.768 PM Safari Technology Preview[1584]: Communications error: <OS_xpc_error: <error: 0x7fff7a5e2b90> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7a5e2f40> { length = 22, contents = "Connection interrupted" }
}>
5/17/16 1:58:59.769 PM Safari[595]: Communications error: <OS_xpc_error: <error: 0x7fff7a5e2b90> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7a5e2f40> { length = 22, contents = "Connection interrupted" }
}>
5/17/16 1:58:59.770 PM Maps[1902]: Communications error: <OS_xpc_error: <error: 0x7fff7a5e2b90> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7a5e2f40> { length = 22, contents = "Connection interrupted" }
}>
5/17/16 1:59:00.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2213 [sandboxd]
5/17/16 1:59:01.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2267 [com.apple.Safari]
5/17/16 1:59:02.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2214 [coresymbolicatio]
5/17/16 1:59:03.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1
5/17/16 1:59:03.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2333 [MTLCompilerServi]
5/17/16 1:59:04.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ClearFeatureInterruptEndpointHalt] -- successfully posting another read for the mInt0InterruptPipe -- mInterruptPipeInOutstandingIOCount = 1 -- this = 0xe800
5/17/16 1:59:04.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2241 [recentsd]
5/17/16 1:59:05.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2244 [systemstatsd]
5/17/16 1:59:06.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][InterruptReadHandler] -- Received kIOReturnNotResponding error - retrying: 1
5/17/16 1:59:06.000 PM kernel[0]: memorystatus_thread: idle exiting pid 2237 [reversetemplated]
5/17/16 1:59:07.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ClearFeatureInterruptEndpointHalt] -- successfully posting another read for the mInt0InterruptPipe -- mInterruptPipeInOutstandingIOCount = 1 -- this = 0xe800[doublepost=1463702570][/doublepost]Has anyone here tried disabling Safari Suggestions? Try it.
These freezes that you have gotten the last couple of month, are they 100% freezes, ie, you CANT move any window or press any menus etc? Some freezes, especially when getting the 100% utility bugs, you can often press an menu item and that item will show up in a 1 minute or so, also, the clock will also update when you have the 100% bug.
With the bug that this thread is about, you get nothing of the above, everything gets in a permanent freeze state, windows, apps, menu items, clock, everything, basically, it acts like a screenshot in time and no user input (except moving the mouse is possible)
Its important to differentiate these 2 bugs, these are 2 very different issues
This was Safari Technology Preview that crashed? I have been saving all my logs/sysdiag from every freezing event, and its really hard getting a good overview and comparing all the logs, i wish Apple had a better log system, or an app that you could import all the logs, mark events AND most importantly time series event so it would be possible to easily compare multiple services and their respective state that occurred within a specified timeframe, that what, we could basically get a "frame by frame" history leading up the crashes and freezing. Its possible to put timestamps into the Console Utility but way way way to limited.
Now, everything is just dumped into folders and text files, usually just i mish-mash of events, its really hard to troubleshoot stuff now.
Have you saved any sys-diagnoses if you had one of those permanent freezes?
I have tried alot of stuff, nothing works
BUT, i have been on a mission for the last 4-5 days, saving process history every 5 seconds, putting them in a per process set and in a time series structure so i can compare all the sample sets and put breakpoints with offset (+-1 minute from the freezepoint). The most interesting part, for me atleast, is when viewing "top" (i save "top" every 5 seconds too), and what every freeze event that required a hard restart several WebKit processes are stuck and even more interesting is that the WindowServer is reporting its state as "stuck" at every datapoint AFTER the breakpoint, before the breakpoint it is mostly reported as "running" and "sleeping", it has NEVER been reported as running or sleeping AFTER the breakpoint, never.
WindowServer gets a "stuck" status when everything is fine too, its not that abnormal to get a "stuck" status and then after a few ms or seconds it goes back to either running or sleeping, but i find it curious that it never changes its status after the system has frozen (the system is still running in the background but does not respond to any mouse-clicks or any keyboard-inputs, so, so frozen should really be used loosely, its not responding to ANY user input, music still running etc etc, we all know this freeze by now i think)
Just now i looked at the "top" report from my sysdiag i did months ago and it is the same thing there, WindowServer is stuck on every sampletime (sysdiag collects a couple of "top" and then log it), i did run a sysdiag just now and it is mostly reported as sleeping.
If anyone is curious, here is my "top" logs from sysdiag, search for "WindowServer"
2016-04-10 on 10.11.4, computer completely frozen (notice WindowServer are stuck on all samples)
http://jespera.se/temp/top_2016-04-10.txt
2016-05-20 on 10.11.5, computer works as expected (notice WindowServer are running/waiting on all samples)
http://jespera.se/temp/top_2016-05-20.txt
Last edited:
No, not a 100% freeze as I can still move my mouse and open Launcher. However, I cannot open any new apps or even open Finder, just get a beach ball. I haven't seen any reference to this other bug you mention. Care to enlighten me?
Well, its hard to say if there even exist a reference because is more of a general bug, from time to time you see people reporting 100% ram usage (from memory leaks, not utility), 100% CPU usage from stuck services making their Macs unresponsive, sluggish and with excessive beach balling etc, i cant pinpoint whats cause it or who it affects but i see several new threads about it each day in various forums
Anyways, after installing 10.11.6 PB1 i got a new record, all other versions since 10.11.4 betas and up until now have started freezing after a minimum of 30 minutes of uptime, sometimes even a day could go past without a freeze, the new record however with 10.11.6 PB1 is 5 minute uptime before freezing, 3 times now in a row my Mac completely frooze (mousemovements still possible) and now for the 4th reboot Safari did not even load all my opened tabs before freezing again
Apple going backwards on this bug....