Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
 
  • Like
Reactions: camelia
On my iMac late 2012 with 24GB of RAM, I was seeing 12GB allocated immediately after the 005 update.
I saw a post stating that running Onyx solved that (thought; Really?!) but tried it (with remove all caches etc set), and now Activity Monitor shows normal memory usage, normal as in similar to before the security update.
YMMV, but try it?
 
  • Like
Reactions: camelia
On my iMac late 2012 with 24GB of RAM, I was seeing 12GB allocated immediately after the 005 update.
I saw a post stating that running Onyx solved that (thought; Really?!) but tried it (with remove all caches etc set), and now Activity Monitor shows normal memory usage, normal as in similar to before the security update.
YMMV, but try it?

Can you elaborate on the settings you used for Onyx to relieve the excess memory usage? Also, this is the Onyx you are referring to:
 
  • Love
Reactions: camelia
2017 21' iMac with 8 GB RAM was almost unusable after that update.

I tend to use OnyX to clear/rebuild all caches and indices after every incremental updates - be it the .X ones or these security updates. Tried it here too. It took forever for the app to launch and even longer to finish its tasks. That was the first time I'd seen this behavior with OnyX, after more than a decade of use.

After a mandatory system restart, things were still sluggish and stuttering - although overall performance had noticeably improved. Left the machine in that state, and went out after some chores. When I came back to it, everything was working properly, just the way it was before the update. No more excessive memory compression, no more performance issues, etc.

Not sure if that little housekeeping I did with OnyX did the trick, or if it was the system itself that finalized whatever it was consuming the memory for while I was away. Still, thought I'd share the experience in case it helps anyone else. Will report back if the machine starts misbehaving again.
 
So I just go with the defaults?

1601135970990.png
 
It seems that a few posters in this thread experienced problems similar to mine with Security Update 2020-004: boot-time and/or periodic UI "freezes", tccd process crashes, tccd errors and respawns shown in system.log.

Have any of you been brave enough to try Mojave Security Updtate 2020-005? Did it cause the tccd/UI freeze problems again or is it OK?

I did not see any change with Update 2020-005. It is still crashing and freezing for me at about the same frequncy as I experienced in 2020-004.
 
  • Like
Reactions: Brian33
Theres also a supplemental update that is available for Mojave that i am hesitant in installing, My 2019 iMac has been rock solid except for having difficulty waking up from sleep after being asleep for a long period of time (usually 24 Hours or so), it requires me to click the power button on the back of the iMac to wake it up from sleep and it has been exhibiting this behavior since i purchased it. Do you think the Mojave supplemental update or the security update could possibly fix this specific annoyance or most likely has nothing to do with? I've gotten used to this sleep behavior on my iMac but perhaps Apple silently fixed in with one of these updates
I have had the same situation with my early 2015 MBA, but never considered it a problem. It went away with security update 2020-002. However, I have not updated to any further security updates since, because of graphics and other problems; described herein.
 
  • Like
Reactions: camelia
I have had the same situation with my early 2015 MBA, but never considered it a problem. It went away with security update 2020-002. However, I have not updated to any further security updates since, because of graphics and other problems; described herein.

Isn't you macOS vulnerable without the missing security updates?

Camelia
 
Isn't you macOS vulnerable without the missing security updates?

Camelia
Possibly. However, I have a backup if I need it, but I do not have grief with the latest security update, 2020-005 and the previous ones.

Update: I did update to Safari 14 only.
 
Last edited:
  • Love
Reactions: camelia
aaronraimist and others that have encountered a UI "freeze" after bootup and login to desktop: I seem to have resolved my problem by uninstalling Dropbox (deleting Dropbox.app) and re-installing it.
(EDIT: I think I also had to manually delete Dropbox from the System Preferences-->Security&Privacy-->Privacy pane.)

I started getting this problem after installing Mojave's Security Update 2020-004, and it also occurred with Security Update 2020-005.

After bootup and initial login (and I think periodically about every hour after that) the User Interface would stop responding to mouse clicks and keyboard input for a minute or so -- then suddenly process all the input. The timing was associated with repeated messages in the /var/log/system.log file about the com.apple.tcc.system process:

Aug 25 14:17:03 imac com.apple.xpc.launchd[1] (com.apple.tccd.system[3708]): Service exited due to SIGABRT Aug 25 14:17:03 imac com.apple.xpc.launchd[1] (com.apple.tccd.system): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

At the same date and time there would be crash reports with names like "tccd_2020-09-26-180449_imac.crash" in Console.app-->System Reports, showing crash information for the tccd process.

On my system, tccd would crash, be respawned, and crash again, seven times in a row within a minute's time. Apparently this repeated crash/respawn cycle was causing the UI freezes. I could reproduce the issue by just rebooting and logging in again: within a minute of logging in, a new freeze would happen along with the above mentioned messages and seven new crash logs.

The tccd process is for Transparency Consent and Control. It has to do with items in the Privacy tab of the Security & Privacy System Preferences pane (according to this article).

I tried a lot of things to prevent these UI freezes/tccd crashes, but what seems to have worked (other than rolling back the security updates) was uninstalling Dropbox.app, verifying that the freezes no longer occurred, and then re-installing Dropbox. I had previously checked my Dropbox version and it was up to date -- at least, so I thought at the time. Perhaps I was mistaken.

I am almost certain that my old installation of dropbox had a user "launch agent" (in ~/Library/LaunchAgents/com.dropbox.DropboxMacUpdate.agent.plist) to run "DropboxMacUpdate" every hour (3625 seconds) -- but now I see in my new installation that the launch agent .plist file is no longer there. I suspect that the running of the launch agent at login and every hour was causing the tccd process crashes.

Hope this helps someone else.
 
Last edited:
  • Wow
Reactions: camelia
Very interesting I checked today to update Mojave with the Security Update 2020-005
that I skipped -waiting few days is a good practice-when I updated Safari 14 and it doesn't appear any longer!

Yes, Apple pulled the update after such a disaster🤞
 
Last edited:
  • Like
Reactions: camelia
Problems with system freezes due to TCCD crashes were resolved in Security Update 2020-007.
 
  • Like
Reactions: Brian33
Awesome thanks for the update. I've tried every security update hoping that one would fix it but I hadn't tried 2020-007 yet.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.