Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Which is ludicrous, given the changes slipstreamed into 10.10.3.

There's nothing new about how Apple is handling this update. Safari 6.1.6 is only for 10.8.5 and Safari 7.1.6 is only for 10.9.5. Apple doesn't continue to issue patches for versions of OS X earlier than the most recent minor version– 10.8.5, 10.9.5, and 10.10.3, in this case, and never has.
 
I think you are the only one expierecing this, Safari should jump ship on you ;)

See that user "severe" has the same issue.... But 2 out of million users?

Actually, when I Googled to see if other people had it, there were quite a few. I restarted my MBP after this update and haven't had the problem since, thankfully. I'll try turning WebGL back on and see how it goes. It was really awful for a while so I had some kind of glitch going on. I agree that it was probably something weird happening in my personal system, like most issues people have, but I couldn't figure out what it was. I RARELY have the upgrade issues I hear other people have on here whenever there is a new OS X or iOS. At any rate, I'm all good now.

BTW- you shouldn't poo poo people who have issues you don't have. After one recent OS X update, I noticed an issue with the timeline layers in Motion where the layer names didn't line up with the timeline sections anymore, which made it hard to work on items. I brought it to Apple Support's attention and the rep checked it on her system where she could look at in in an earlier version of the OS and confirmed that the upgrade caused the issue. She sent the issue up the chain. So I found a bug! Thankfully, they fixed it in a later upgrade. Sometimes a problem on someone's system actually IS an Apple problem but it's very specific to that person's workflow and not yours.
 
Last edited:
What's the point of patching Safari on Mav and ML if they aren't going to fix the Rootpipe vulnerability? It's good that they've patched it, but the latter problem leaves non-Yosemite users at risk.

Better to keep getting the other fixes than nothing at all I suppose - however the Rootpipe Vulnerability wasn't actually fixed in Yosemite.

The security researcher that pointed out the Rootpipe vulnerability to Apple worked around Apple's Yosemite "fix" (I believe he said on the plane ride home) and exploited it again (so its not really fixed for any version of OS X yet).

http://www.zdnet.com/article/apple-failed-to-fix-rootpipe-backdoor-flaw-warn-researchers/
 
This does seem to have helped with Safari issues, however, my Mac turned itself off today. Turns out it got too hot using Flash. This has only been happening since 10.10.3. (I got Macs Fan Control to see what temp my Mac is running at, and when I started up after it shut itself off, and it started running video again, I watched the temp and it was hovering around 88ºC...I think it shuts down over 90º).

So, some months ago, I was about to do a clean install of Yosemite and was trying to avoid installing Flash. I tested how much CPU Flash uses on my Mac, Safari used the least CPU power (fastest), Google Chrome (using it's Flash emulator or whatever) used a lot more CPU (I think it was like 20-30% more). I don't have Chrome, I hate google, so deleted it when I found Safari to be better, (also hate Flash, but, only way to watch some video still), but, anyone know, has Google made improvements to Chrome's speed/CPU usage recently? Maybe I should try it again?
 
You need to install safari adblock for that. That'll stop the livejasmin popups.

Doesn't stop it from happening in iOS though...unfortunately.

Though I did figure out how to get the app store to stop popping up (disable installing apps in restrictions). It's a kludge but it's not like I go on there every day. The only downside is not getting immediate app updates but I can push those through desktop iTunes anyways if need be.

----------

This does seem to have helped with Safari issues, however, my Mac turned itself off today. Turns out it got too hot using Flash. This has only been happening since 10.10.3. (I got Macs Fan Control to see what temp my Mac is running at, and when I started up after it shut itself off, and it started running video again, I watched the temp and it was hovering around 88ºC...I think it shuts down over 90º).

So, some months ago, I was about to do a clean install of Yosemite and was trying to avoid installing Flash. I tested how much CPU Flash uses on my Mac, Safari used the least CPU power (fastest), Google Chrome (using it's Flash emulator or whatever) used a lot more CPU (I think it was like 20-30% more). I don't have Chrome, I hate google, so deleted it when I found Safari to be better, (also hate Flash, but, only way to watch some video still), but, anyone know, has Google made improvements to Chrome's speed/CPU usage recently? Maybe I should try it again?

My recommendation: Even if you don't like Chrome, keep it around just for cases where you need Flash. That way you get the benefit of preventing unnecessary CPU usage during your normal browsing (since Flash isn't technically installed), as well as not having to regularly update Flash (Google keeps it up-to-date automatically along with regular Chrome updates). It's the best compromise I've managed to find and I wish I could do the same with Java plugin (though I can't even remember the last time I used a web applet).
 
I'm experiencing it as well. I'm not sure what caused it but within the last week or two Safari began to freeze/hang on a lot of pages I had always visited regularly.

Or should I say, was experiencing it. After installing the update last night I tried a few of the pages it was having trouble with (flash/ad heavy) and it was back to being smooth. I hope it was a fix and I wasn't just lucky.

(Actually now that I think about it, I tried installing Firefox and that browser had the same problems. Maybe a bad Flash version is the true culprit?)

Guess so. :D

----------

Actually, when I Googled to see if other people had it, there were quite a few. I restarted my MBP after this update and haven't had the problem since, thankfully. I'll try turning WebGL back on and see how it goes. It was really awful for a while so I had some kind of glitch going on. I agree that it was probably something weird happening in my personal system, like most issues people have, but I couldn't figure out what it was. I RARELY have the upgrade issues I hear other people have on here whenever there is a new OS X or iOS. At any rate, I'm all good now.

BTW- you shouldn't poo poo people who have issues you don't have. After one recent OS X update, I noticed an issue with the timeline layers in Motion where the layer names didn't line up with the timeline sections anymore, which made it hard to work on items. I brought it to Apple Support's attention and the rep checked it on her system where she could look at in in an earlier version of the OS and confirmed that the upgrade caused the issue. She sent the issue up the chain. So I found a bug! Thankfully, they fixed it in a later upgrade. Sometimes a problem on someone's system actually IS an Apple problem but it's very specific to that person's workflow and not yours.

Well, it not about poo pooing people, but some people start cursing OSX for any reason. It is rare that just a few people experience this problem, therefor they should first consider there own mistakes on their computer before blaming Apple and or Safari. Happy to hear that it works for you now.
 
I installed Safari 8.0.6. No issues with Yosemite 10.10.4 so far.
 
Last edited:
The update seems to have installed itself on its own on my computer (maybe as I logged out of my user account earlier today).
 
If you are going to experiment with installing a version of safari onto a system for which it is not intended I would suggest installing some other browser there too like firefox or chrome before doing so.

Otherwise I would suggest NOT doing so.

You might have got away with it now, but you probably wouldn't want a system with no functional browser at all.

My system is always backed up, I can always revert back :)
 
There's nothing new about how Apple is handling this update. Safari 6.1.6 is only for 10.8.5 and Safari 7.1.6 is only for 10.9.5. Apple doesn't continue to issue patches for versions of OS X earlier than the most recent minor version– 10.8.5, 10.9.5, and 10.10.3, in this case, and never has.

Which is why major updates like Photos should have their own release/install, instead of being slipstreamed in an OS point release. This is 2015, even Microsoft has (mostly) stopped doing that sort of thing in point releases. :(
 
Which is why major updates like Photos should have their own release/install, instead of being slipstreamed in an OS point release. This is 2015, even Microsoft has (mostly) stopped doing that sort of thing in point releases. :(

I agree that it's strange that Apple tied Photos into the OS, but 10.10.3 didn't force anyone to change. iPhoto and Aperture still work fine.
 
Anyone else experiencing huge memory leaks? I watched Safari hog 6 GB of RAM yesterday. After I noticed how sluggish it became, I started up Activity Monitor and watched the Safari process eating up around 200 MB every 3-5 seconds or so. At 6 GB I finally quit Safari. Today the same thing happened, although I stopped it right when I noticed the sluggish behaviour (3,5 GB of RAM used).
 
I agree that it's strange that Apple tied Photos into the OS, but 10.10.3 didn't force anyone to change. iPhoto and Aperture still work fine.
Other apps like Facetime, iBooks etc. are also not shipped separately. There is nothing odd about shipping an OS with a set of bundled applications from Mail.app over Calendar. And saying that new applications should only be bundled with major OS versions is also a rather artificial limitation.
 
Still randomly freezes for me, forcing me to reload pages or just onto Chrome occasionally on my 2011 27inch imac with 256GB SSD 16GB ram running Yosemite. Seven was far better on Mavericks. So much quicker.
 
Still randomly freezes for me, forcing me to reload pages or just onto Chrome occasionally on my 2011 27inch imac with 256GB SSD 16GB ram running Yosemite. Seven was far better on Mavericks. So much quicker.

I assume when you mean 'freeze', you're talking about pages that don't fully load? I've had the same problem for ages with GEM Visa's own website with their logon page. I'm wondering to what extent it is a server/client configuration issue given that it only impacts specific websites I visit rather than it being random websites.
 
It's random websites for me. The progress bar just stops and I have to hit the cancel/reload button, if that doesn't work Chrome usually does. Plus loads of websites have loads of 'A's in boxes where there should be information. Safari 8 has been pretty crap, on my mac at least.
 
Doesn't stop it from happening in iOS though...unfortunately.

Though I did figure out how to get the app store to stop popping up (disable installing apps in restrictions). It's a kludge but it's not like I go on there every day. The only downside is not getting immediate app updates but I can push those through desktop iTunes anyways if need be.

----------
My co-worker has this happening on her Ipad. I have no way of helping her. So freaking crazy.
 
I agree that it's strange that Apple tied Photos into the OS, but 10.10.3 didn't force anyone to change. iPhoto and Aperture still work fine.

Works fine for those who had updated versions of iPhoto but for anyone installing 10.10.3 over Mavericks they now have a big blot over the iPhoto app and it is rendered useless. If Photos had been an optional upgrade those users would have been able to update iPhoto first before upgrading to Photos. Can't even download the iPhoto update now.
 
For some reason, after updating to OS X 10.10.3, Safari wouldn't even open until I updated it. I originally thought I had updated Safari and that it the update had broken it, but apparently, "Update All" in the App Store didn't update all.

wait -- so if apple doesnt patch new vulnerabilities, they get hated on. but if they do fix them, they get....hated on?

nice hater logic.

1. He never hated on anything.
2. It's bad that those vulnerabilities exist in the first place.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.