I've noticed in Activity Monitor that the "Security Agent" process is consuming 100% of a CPU core. What's more is that there are 4 "Security Agent" processes running, each at 100%!
I've noticed this problem happens every 7 days or so and I can't figure out why. The only reason I notice is that I come up to my iMac and the fans are running trying to cool the thing as it struggles with the runs away "Security Agent" processes.
Please help!
iMac 27", 10.15
I had this issue on a 2019 MacBook Pro 16 with only one user account.
I had the issue with and without a monitor attached.
I didn’t have WiFi turned on as I used Ethernet via Thunderbolt with a CalDigit TS3
Based on my own experience, I don’t believe multiple accounts, WiFi or external monitors are at the root of the problem.
I have this issue too, it happens when my 3 year old son is "on" the computer. he sits at the login screen mashing the keyboard and struggling with the mouse until he manages to click the icon with his face on to log on (with no password)
When he leaves and I log him off, and log back onto my account, I can see (and hear via the fans) the rogue processes..
From what i read of other peoples posts, its definitely related to my sons account.
There's clearly a bug in the code somewhere. Needs to be fixed by Apple...
Related to Airport network. "airportd" is a daemon/driver. Call Apple to find out more.
Today i observed same behaviour on my MBP 16". Same logs - restart of machine did stop it. I am on 10.15.2 as well.
not sure whats behind this behaviour. Cant move to LAN as mostly i am on Wifi
I force stop the process in Activity monitor, but I am annoyed as it keeps coming back. I also have not been able to sort out what is causing it. Never happened before I upgraded to Catalina. Most annoying issue.
Some additional Information. I've noticed these messages in the Console, under Log Reports, wifi.log. This repeats over and over again.
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events.private, will not register for event type 100
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events.private, will not register for event type 101
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events, but allowing anyways for event type 7
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events, but allowing anyways for event type 2
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events, but allowing anyways for event type 1
Tue Dec 10 11:02:50.848 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events, but allowing anyways for event type 5
Tue Dec 10 11:02:50.849 <airportd[246]> ERROR: SecurityAgent (5615) is not entitled for com.apple.wifi.events, but allowing anyways for event type 6
Ha ! Coincidentally, I wanted to type inn my earlier message "one diagnose". Because there can be multiple causes and situations for such a problem, just like with a headache or nausea...
You need to find a pattern which triggers the problem to occur, or to vanish. That takes time and perseverance. But only with that information, a developer, engineer, or doctor might be able to come up with a thorough solution.
Agreed.
I tried to track it down and solve it for two weeks, then returned the machine as it’s random behaviour didn’t fit well with my work schedule.
The Apple tech agreed there was an issue and refunded despite the model being a made to order configuration.
I will buy another in the future, it would be nice to know that this issue (at least) is identified and addressed in the meantime.
There seems to be many happy users out there, in comparison to the unlucky few in this discussion.
Oooh, that's too bad !
A really random behaviour is often a dire indicator of something technically malfunctioning or breaking down, in stead of an unexpectedly conflicting factor or an incorrectly programmed routine. So it's like you said: you must have been one of those unlucky users...
Maybe the Touch ID hardware to run the authentication was not thoroughly working and intermittently disturbing the system, causing that SecurityAgent process to slip into an endless cycle ?
I can assure you, I haven't yet run into any other serious problems with the MacBook Pro 16" (also BTO).
Love that machine so far !
Same problem here: nicely spec-ed 15'' 2018 MacBook Pro.
Never spotted it before (and I do tend to keep an eye on Activity Monitor quite regularly) but we did use another user account earlier today, something we hardly ever do on this particular machine.
I have the same problem on a 2017 MacBook Pro with i5 and other wonderful stuff inside, with 10.15.3 Catalina installed.
The problem appears randomly, I tried to follow Apple's suggestion and I cleaned my cache by booting in safe mode; now obviously the MacBook works fine, but I can't tell if the problem is solved.
Here's my table of process
Did anyone find a fix for this annoying issue?
I have this problem as well the security process took 100% of CPU with the Catalina..........and I still haven’t got the reason why
The issue is back. I am now thinking it is related to my daughter logging into the iMac with her account which is under parental control. Really disappointing.
you should install windows， Macos is not mature
I haven't observed since last 3 weeks, this issue is gone for now.
My fans are always off mostly unless i connect monitor or running some intensive jobs.
Security Agent causing high cpu
