Interesting. I’m tired of testing workaround but maybe Safari 14 is at least responsible for cDock crash?
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.
Security Update 2020-005
- Thread starter Earl Urley
- Start date
- Sort by reaction score
Unfortunately no... I would have to restart again from the beginning on my (now useless) USB3 test clone. But maybe you’re onto something.
Hmmm! Is there a way to uninstall Safari 14 (like with AppCleaner) and reinstall Safari 13, maybe with Pacifist? I don’t know if the Safari 13.02 package I have contains all the required files??
Not sure 100% but I guess every Safari package contains the whole Safari app. I found an official link for downloading Safari 13.1.2 but it is not working anymore.
But regarding removing Safari to replace it by an old one, I dunno how it could be done properly (excepted rolling back to a previous version of Mojave, which overwrite Safari, then installing a new Safari version from your .pkg).
Ah ah! Uninstalled Safari 14 via AppCleaner (checked all elements). Reinstalled Safari 13.1.2 via Pacifist. This is on my "test drive" with 2020-005 installed BTW.
Ran:
Memory usage is back to (it seems to me) much normal amount, maybe a tad higher than before update. WindowServer is back to under 100mb.
And...cDock works again!
[automerge]1601300570[/automerge]
Ran:
Code:
sudo update_dyld_shared_cache -root / -forceMemory usage is back to (it seems to me) much normal amount, maybe a tad higher than before update. WindowServer is back to under 100mb.
And...cDock works again!
[automerge]1601300570[/automerge]
See my last post. Doable, I now have 13.1.2 reinstalled on top of 2020-005.
Wow, do you mean 005 update is fine if you don't use Safari 14? So if yes it looks like the behavior I got is confirmed: installing update (as 004 or 005) on a system already having Safari 14 will cause memory issues!
edit: but installing update on a system having Safari < 14 would be fine so.
It seems... Too soon to draw serious conclusions but Safari 14 seems to be part of the culprit. I still have a tad higher memory usage at boot. On my 2020-004 SSD, 3.90 - 4.00 at boot vs 4.5 on the test drive.
Also, not seeing anymore:
Code:
Finder[411]: objc[411]: Class asn1IntegerToken is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x7fffb37156a0) and /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x11ad9cf70). One of the two will be used. Which one is undefinedIndeed... the best idea right now would be to stay away from Safari 14 and 2020-005 so.
Thank you for your feedback and your tests also.
I've just looked inside 2020-005 with Pacifist:
- There are updated files for Safari in PrivateFrameworks. I don't know if it could wreak havoc on top of Safari 13.1.2?
- There are updated files for Safari in PrivateFrameworks. I don't know if it could wreak havoc on top of Safari 13.1.2?
I can not attest 'cause my USB3 test drive is "sluggish" compared to my main SSD. One would have to compare on the same drive.
Anyway, I'll stay on 2020-004 with Safari 14 for now...
Safari isn't just the app itself- there's a lot of under the hood parts. There's no way to reinstall Safari 13 at this point.
That sounds great!
I have reported the cDock crash to Mr. Baird, the developer, and he gave me a link to a beta version 4.30 that does not crash on start up, but still is work in progress as it does not implemnt themes yet, and running cDock just crashes, requiring a reboot. So your success is tempting.
How to get Pacifist to work? What installer did you aim it at that has Safari version 13.1.2?
I meant 13.1.2.
I know there is a lot under the hood but hey, it works on my side.
Now, after a pass of Onyx cleanup, memory usage is down to what it was prior to 2020-005!
It worked for me once Safari 14 was replaced with 13.1.2.No change for me after Onyx cleanup
Earl Urley wrote, "Also reported the bug to Apple via their feedback page, but I doubt I'll ever hear back from them." My sentiments exactly Earl. I wouldn't count on Apple addressing this issue anytime in the near future, if ever, no matter how many bug reports they receive. The vast majority of Apple employees, whether at Cupertino or working from home, have been using Catalina for over a year (or iPads), unlike those of us still on Mojave, and could care less about this problem (from what I gather Tim Cook has been using an iPad pretty much exclusively for some years and most likely has only a vague memory of what Mac OS even looks like). Also, Apple is busy getting Big Sur ready to ship, preparing the transition to ARM (sorry, Apple Silicone) Macs and is still occupied with fixing the numerous bugs in iOS 14 (and some in Catalina). Keep in mind of course that Apple's mobile devices are its chief money maker by far and therefore its top priority and probably always will be. I highly commend some of the posters here, especially Maximumsportz, pierresparten and others for providing some good technical advice about how to potentially fix this issue on your own while waiting, perhaps indefinitely, for Apple to do something.
Tbh, if your Mac is running as normal and not running out of memory or struggling to run apps, is it a big issue. AFAIK the amount of used ram in my Mac is what it needs.....that’s it.
OK it was using 9gb with minor things open, but I opened LW3D and Davinci and it only increased to 11gb.
OK it was using 9gb with minor things open, but I opened LW3D and Davinci and it only increased to 11gb.
I am running 2020-005 and have just installed the new Safari 14.0.1 beta and my system is back to normal!
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?)
Hello @pierrespartan , you are saying one thing, I recently installed Safari 14, it working very badly (recurring error when loading sites), I realize that I had not updated my Mac with the 2020-04.
I'm installing this update thinking it will fix my issue with Safari 14, but nothing helps. I realize that since (installing Safari 14 or updating 2020-04?) My Mac is consuming 10% more memory than usual.
For others, I haven't installed 2020-05, which makes me say that you are right in the order of installation.
For my part I did:
Safari 14> 2020-04 and I have a memory problem.
I'm installing this update thinking it will fix my issue with Safari 14, but nothing helps. I realize that since (installing Safari 14 or updating 2020-04?) My Mac is consuming 10% more memory than usual.
For others, I haven't installed 2020-05, which makes me say that you are right in the order of installation.
For my part I did:
Safari 14> 2020-04 and I have a memory problem.
@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
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
Safari 14.0.1 beta didn't address the inability to make a new user nor the high memory usage on the test virtual machine I'm using.
Please read one of my previous post carefully, as I said, Safari 14 works fine BUT it causes troubles if the following requirements are:
- Safari 14 already installed
- performing any Security updates
-> in that particular conditions (or order), here excessive memory usage happens.
Of course, if you installed Security Update first, then Safari 14, it's fine... until you install a new Security Update! (because you'll perform this new Security Update with Safari 14 already installed)
[edit] that's why re-installing Mojave (which brings back Safari 12.something), then Security Update (004, forget the 005 for now) is fine.
Hope I'm clear enough though
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.