Just switched to Firefox. We'll see how that goes. Luckily this machine can be used as a monitor for when I get a new computer
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
Check this thread: https://discussions.apple.com/thread/7687562?start=345&tstart=0
WebKit is the culprit, that means anything that uses it (Safari, iTunes) can cause a freeze.
Never had a problem with Chrome, Firefox should work as well; this is the only workaround right now.
WebKit is the culprit, that means anything that uses it (Safari, iTunes) can cause a freeze.
Never had a problem with Chrome, Firefox should work as well; this is the only workaround right now.
Yes but they forked it years ago and are using a custom rendering engine so they probably "missed" this bug
In my case it was the SoundflowerSigned.kext which caused the hang. Roxio software installed this extension in
/System/Library/Extensions.
/System/Library/Extensions.
Has for me, so far, but only a couple of days since I made the change.
Edit: Over a week now and still no freeze, looks like we have a winner!
Last edited:
What about the Security Update 2016-003 Supplemental for 10.11.6 from 17.01.2017 .
https://support.apple.com/kb/DL1908?locale=de_DE
Apple wrote in the update notes:
"Update fixes a kernel issue that may cause your Mac to occasionally become unresponsive."
This sound a bit like the freezing problem we facing with since 10.11.4 . But how knows, maybe the just referencing to a different problem?
Did someone try this last update with El Capitan and can share some experience here?
https://support.apple.com/kb/DL1908?locale=de_DE
Apple wrote in the update notes:
"Update fixes a kernel issue that may cause your Mac to occasionally become unresponsive."
This sound a bit like the freezing problem we facing with since 10.11.4 . But how knows, maybe the just referencing to a different problem?
Did someone try this last update with El Capitan and can share some experience here?
Me too so far. Was sort of a chore to switch back from Chrome but hey! No freezes yet.
It gets a lil laggy on cpu intensive webkit stuff but I still only have 4gb RAM so that may be just that.
I have tried this, and the machine will not reboot. nothing works but the power button. Safari is the main culprit, but it will occasionally lock without Safari.
FWIW, I'm going to try this. I had switched over to Chrome and hadn't had a freeze in 3 days, but I'm uncomfortable with the security of a Google product.
I'll report back on how the Safari compositing flag disables works works out.
EDIT: Implemented the fix as stated above and have successfully used Safari for many hours now. Thanks! to whoever developed it.
Last edited:
Yeah, i started up my iMac again after a couple of months retirement and i tried the fix and so far it have worked, i have almost 3 weeks of uptime now, over 1 year since i could get that uptime without any freezes.
Such a shame that the backlight on my iMac doesn't work now that we finally have a fix but on the plus side, sometimes when i wake it up from sleep the backlight starts working for a minute or so; so i can enjoy a nice Philips Ambilight style backlight behind my ACD
(i wonder if it is worth trying to fix the backlight but i guess its expensive as ****)
Anyways, nice that there is a fix that works, FINALLY
Such a shame that the backlight on my iMac doesn't work now that we finally have a fix but on the plus side, sometimes when i wake it up from sleep the backlight starts working for a minute or so; so i can enjoy a nice Philips Ambilight style backlight behind my ACD
(i wonder if it is worth trying to fix the backlight but i guess its expensive as ****)Anyways, nice that there is a fix that works, FINALLY
I didn't have this issue until I updated to Sierra 10.12.4. I used Firefox for a day, but I'm really not a fan. Tried this fix in Safari, and problem seems to have vanished! The Freeze happened in only a couple of sites with lots of graphics, but was very repeatable. Glad this worked. Many Thanks.
Lou
I recently ran into this problem after the 10.12.4 update. Safari would crash on this one page. Only a hard shutdown would solve it.
I found that by turning off JavaScript, it would solve the problem. It's not a real solution though as just about every webpage out there uses JavaScript. None of the other browsers (Chrome, Firefox, Opera, ect.) were having this problem on the exact page that would crash Safari.
After some searching, I found one person who posted a crash report and it appears the the JavaScriptCore was crashing. In my opinion, I think Apple's new JavaScript engine which was supposed to make JavaScript run faster is the culprit. Just a guess though.
Still, I can no longer use Safari. Now I have to move to another browser but each one has their own issues. I guess I have the choose the one I have the least objections to. Fun times.
I found that by turning off JavaScript, it would solve the problem. It's not a real solution though as just about every webpage out there uses JavaScript. None of the other browsers (Chrome, Firefox, Opera, ect.) were having this problem on the exact page that would crash Safari.
After some searching, I found one person who posted a crash report and it appears the the JavaScriptCore was crashing. In my opinion, I think Apple's new JavaScript engine which was supposed to make JavaScript run faster is the culprit. Just a guess though.
Still, I can no longer use Safari. Now I have to move to another browser but each one has their own issues. I guess I have the choose the one I have the least objections to. Fun times.
Not sure he has the same problem as us, i have not seen any evidence that the javascript engine is the reason for the "crashes", i've turned off javascript a billion times before and still got the freeze. The only fix for me has been the solution that superduperultra posted/linked, not a single freeze since then.
I tried disabling the hardware accelleration and it didn't make a difference. Only the Javascript. Once they updated the Safari Technology Preview that I also have, the problem finally went away. It appears they were tweaking some things and something got out of whack.