Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Madrich wrote: "My only thought here, is why is this happening? Does not Apple care anymore?" The answer to your question is probably no, they don't care that much anymore about Macs. Read my post from earlier today on this subject. One thing I would add to that post is to remind everyone that it took Apple four long years to more or less admit that the awful, unreliable butterfly keyboards on their newer laptops were a disaster and finally revert to the old, classic scissors keyboards on all future laptops. While it is true that Steve Jobs could often be an aggressive, sometimes ruthless businessman and manager, it is also true that in the Jobs era the bottom line at Apple was always the quality of the product; that is what mattered. In the Tim Cook era, for all his supply chain expertise and admirable personal qualities, the bottom line is the bottom line.
 
@marioliv66@ Thanks for this clarification. Everything leads to this conclusion: Safari 14 does something bad in the system. Because during my test, I tried one time to install Mojave 10.14.6 (from Recovery, meaning there's no Security Update applied), then I installed Safari 14. Finally I tried to install the 2020-001 (not 004 or 005, but 001!) and... here problems happened once again.

So from what I know/experienced/heard from users: Safari 14.0 breaks any Security Update you can perform, and perhaps Safari 14.0.1 solved this.

edit: here the changelog of the new Safari beta, maybe something interesting somehow: https://download.developer.apple.co..._Mojave_beta_1/Safari_14.0.1_Beta_1_Notes.pdf

@pierrespartan, I was on the same track! This is the flow that I've confirmed.

  • Test Steps
  • 1. 10.14.6 (18G103) Base Install
  • 2. Install Security Update 2020-005 Only = No Problem
  • 3. Install Safari 14.0 = No Problem
  • 4. Install Security Update 2020-005 again = PROBLEMS!
Safari 14.0 IS involved in this but ONLY when installed FIRST and the 2020-005 is applied AFTER it.

Next test - Can I install Safari 14.0 first then the 2020-004 Security Update after and still be ok.

I am tracking all latest updates here.

 
  • Like
Reactions: BrotherJerome
@pierrespartan,

I was on the same track! This is the flow that I've confirmed.

Next test - Can I install Safari 14.0 first then the 2020-004 Security Update after and still be ok.


Hello MrMacintosh! Well I already tried, Safari 14.0 FIRST, then SU 2020-004 SECOND -> I got the same symptoms! (high memory usage at least)

I've done this also with SU 2020-001, same symptom too, if Safari 14 installed FIRST.
 
So as proof of your statement, you are running security patch -005 and an earlier version of Safari? Because from what you are saying, the security patch does not cause this problem, but Safari does. And the only way to prove that is to be running the latest security update right now. Which most of us, are not, for obvious reasons.

For now I'm running 2020-004 with Safari 12.something (the one bundled with Mojave 10.14.6 from Mac App Store or Recovery). Yes, two things:
* Safari 14 seems to break ANY Security Update (I tried with 001, 004 and 005 and every time I got high memory usage with a ton compressed... ) if it (Safari 14) was installed before applying the SU 2020-00X.
* It looks like 2020-005 by itself has some issue too, independently of the Safari version you're using (to be confirmed at that point I guess).
-> edit: hum... looks like 2020-005 itself is fine, if Safari 14 not installed when applying this update, thanks MrMacintosh for this test.

So installing any SU first looks fine, then you can install Safari 14. From there any new SU will be broken, so I guess staying far from Safari 14 is the best thing to do, at least until a fix.
 
Last edited:
  • Like
Reactions: bernuli
Hello MrMacintosh! Well I already tried, Safari 14.0 FIRST, then SU 2020-004 SECOND -> I got the same symptoms! (high memory usage at least)

I've done this also with SU 2020-001, same symptom too, if Safari 14 installed FIRST.

For sure! I am basically confirming what you are saying.

If you install Safari 14.0 First and 2020-004 or 2020-005 Update after = Problems!

So to work around the issue you could do this

Install 2020-005 first then safari 14.0 = no problems

Here is the thing. If installing 004 or 005 after Safari 14.0 causes issues... what is to say that 2020-006 will not cause the same issue? (unless Apple address this issue)


Might be good to just wait a bit.
 
  • Like
Reactions: BrotherJerome
...

Here is the thing. If installing 004 or 005 after Safari 14.0 causes issues... what is to say that 2020-006 will not cause the same issue? (unless Apple address this issue)


Might be good to just wait a bit.

Thanks for your feedback!

For sure, I also recommend to stay with Safari < (strictly lower than) 14 and wait for a fix.
Just in case, do you know an official link to get the .pkg of Safari 13.1.2 (the latest one before 14 if I'm right)?

Because Mojave from Mac App Store or Recovery version come with Safari 12.something only.
 
I found a solution: booting in Recovery mode, then Re-installing macOS Mojave solved this issue for me!

Now my Mac is back to normal behavior. Hope this helps.

[edit] but now I'm back to Security update 4, so I'll wait for a fix before updating again.
Same here!
 
I had the new Security Update (005) and Safari 14 installed, and while the memory usage was quite high, I was willing to live with it as it was mostly stable.

Then I plugged in an external drive I needed to use and the system ground to a halt with one process (icons_something, neglected to write it down) suffering some kind of memory leak and soon grabbing >12gb of memory (and growing continuously).

Reinstalled mojave over the existing and now stable again, normal memory usage, and no prob with the external drive.

One obvious symptom from several reinstalls (Mojave/005/Safari 14) was a very large number of console messages with messages "implemented in both /System/Library/PrivateFrameworks/[more detail] and [similar path but Versions/A/[similar]. One of the two will be used. Which one is undefined". Most/many of these messages seemed related to StoreServices or something like that, but not limited to just one set of frameworks. (Note that without the 005 security update, there are some similar error messages in console, but relatively few; after 005, console/system is just flooded with these almost constantly).

One clue I found was that when making snapshots in terminal (tmutil snapshot), the messages from snapshot had errors related to these 'duelling frameworks.' Without installing 005/Safari, the response from snapshot is just 'created local snapshot with date: [date]". So I think/believe that's an indicator of the issue going on under the hood that's causing all these issues. Hope this helps some others diagnose their problems.

I'm not going to install the updated safari or 005 until there's a revised version, and even then will wait a bit to see (this experience coincided with making other system/hardware changes and upgrading to Mojave from High Sierra, and it's been a nightmare to get it back to stable, with many many reinstall/upgrade/migrate loops).

One question though: I believe the fresh Mojave install doesn't include any of the security updates prior to this one, and Safari is v12.x. I was a bit surprised that system update is not showing the previous security updates and/or safari 13. Should I be worried/trying to install those or ....? Find them on internet or is there some way to force Software Update to show them?
 
One question though: I believe the fresh Mojave install doesn't include any of the security updates prior to this one, and Safari is v12.x. I was a bit surprised that system update is not showing the previous security updates and/or safari 13. Should I be worried/trying to install those or ....? Find them on internet or is there some way to force Software Update to show them?

From a fresh Mojave 10.14.6, MAKE SURE YOU DON'T upgrade to Safari 14 (which may pop up in the Pref. Pane).

Having Safari 13 or 12 on your fresh Mojave IS SAFE to apply the Security Updates ranging from 001 to 004 (I would recommend not applying the 005 one for now until we get more infos).

You can find any Security Update on the Download page on the Apple Website, but for Safari 13 (and so 13.1.2), it doesn't exist on that page anymore as they want you upgrading to Safari 14. I don't have a backup of that version (13.1.2) sadly.

edit: https://support.apple.com/downloads/Mojave-Security-update%202020
 
Last edited:
  • Like
Reactions: armoured
From a fresh Mojave 10.14.6, MAKE SURE YOU DON'T upgrade to Safari 14 (which may pop up in the Pref. Pane).

Having Safari 13 or 12 on your fresh Mojave IS SAFE to apply the Security Updates ranging from 001 to 004 (I would recommend not applying the 005 one for now until we get more infos).

You can find any Security Update on the Download page on the Apple Website, but for Safari 13 (and so 13.1.2), it doesn't exist on that page anymore as they want you upgrading to Safari 14. I don't have a backup of that version (13.1.2) sadly.

edit: https://support.apple.com/downloads/Mojave-Security-update%202020

Yes, absolutely going to wait before applying both Safari 14 and Security Update 005. Also I warn others, somehow in this process one of the preferences for updates got set to automatic updates - caught that in time, phew.

I will likely do the 004 Security Update and wait on everything else. Too bad about Safari 13 but I'm not particularly reliant on Safari.
 
Too bad about Safari 13 but I'm not particularly reliant on Safari.

Well... Safari always worked fine for me, and I always use it (excepted for a few old websites where Firefox is better).
But for sure I would never have expect (please correct this sentence is my English is too bad there ☺) so much issues just by updating an app (Safari)... even if I know, Safari is somehow an entire part of the macOS environnement.

So... Wait and see...
 
I tried to ignore that duplicitous Safari 14.0 update, using softwareupdate --ignore Safari14.0MojaveAuto-14.0, but it still comes back in the Pref. Pane, even after a reboot... (and even well-listed in the ignored software, as the 2020-005 too)

Any clue? Thank you.
 
Hi,
after mojave re installation (NOT an erase disk and fresh install), I installed su 2020-4, and THEN safari 14 (I think I did it after SU, not sure, but no more ram consumption problem).This on my cMP. On my macbook only the SU 4, not safari 14 (still on safari 12 original after re installation)
Does the su 2020-4 take all previous SU updates from 1 inside it ? Or do I need to install all the SU one by one ? (the pref panel only shows /suggests me SU 5 as an available update)
 
Last edited:
  • Like
Reactions: BrotherJerome
Thank you @ClassicII for digging to the root of the problem. I did not have 2020-005 yet, but had already Safari 14 installed
Today I reinstalled Mojave from USB, applied Software Update 2020-005 rebooted and then installed Safari 14.
During installation software update responded that one of the packages has been pulled from the server, but after that error I already had Safari 14 and observe no problems (even screensavers are working fine).

Might it be that Apple already pulled Safari 14 or substituted it with new package?

It took ~45 minutes but now everything seems to be fine with latest security update applied.

I am not sure about memory usage though and WindowServer seems to consume more than it should, however I had 8 different windows with safari opened (6 are minimized) that might lead to WindowsServer consuming more than it should
1601387649244.png
 
Last edited:
I am hoping this is a Safari 14 bug only and once Apple fixes the issue our Mojave installs will go back to normal.

One interesting note, I was looking at my work MacBook Pro with macOS Big Sur beta installed on it and it is reporting WindowServer taking up 360+ MB of memory (hovers between 360MB to 400MB with only a couple of windows open).
 
Thanks for your feedback.

Interesting... so, in other hand (to be sure I understand), your system was slowed down when you had, at the same time, Safari 14.0 AND 2020-005 update on Mojave, is that right?

If yes, if I well-understand, installing on such system the new Safari 14.0.1 beta solved the excessive memory usage, is that right too? (and maybe at the same time solved slow boot and/or other issues reported previously by different users?)

Sorry for the delay in responding.
Yes, I had updated to 2020-005 and Safari 14 and had the sluggishness & memory problems many have reported. I then installed Safari beta 14.0.1, rebooted, and my Mac has been fine since (nearly 24 hours now). I grabbed the 14.0.1 beta from the free developer program. Hope this helps.
 
To anyone who has used the "Recovery Mode" to re-install macOS without wiping the partition/disk: does this still zap your users and their files/settings, or does it just overwrite system files and leaves the rest intact?
 
Last edited:
Thank you @ClassicII for digging to the root of the problem. I did not have 2020-005 yet, but had already Safari 14 installed
Today I reinstalled Mojave from USB, applied Software Update 2020-005 rebooted and then installed Safari 14.
During installation software update responded that one of the packages has been pulled from the server, but after that error I already had Safari 14 and observe no problems (even screensavers are working fine).

Might it be that Apple already pulled Safari 14 or substituted it with new package?

It took ~45 minutes but now everything seems to be fine with latest security update applied.

I am not sure about memory usage though and WindowServer seems to consume more than it should, however I had 8 different windows with safari opened (6 are minimized) that might lead to WindowsServer consuming more than it should
View attachment 961036
Do you just have Safari open?
Try it with just one tab to see how much memory is used.
Your compressed is very high.
 
With this security update (10.14.6), it appears that my ability to use keyboard shortcuts or scroll gestures to zoom in on the screen is no longer working. Can someone verify? Settings\Accessibility\Zoom...
 
Sorry for the delay in responding.
Yes, I had updated to 2020-005 and Safari 14 and had the sluggishness & memory problems many have reported. I then installed Safari beta 14.0.1, rebooted, and my Mac has been fine since (nearly 24 hours now). I grabbed the 14.0.1 beta from the free developer program. Hope this helps.

No worries!
Thanks for your answer.

Just one thing, do you remember in which order you installed this following (?):
* 2020-005 update
* Safari 14.0
* Safari 14.0.1 beta version

So I guess Safari 14.0.1 is in 3rd position, but what's about the other two?
Your answer may help to understand ☺.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.