Accountsd Mac cpu is high

Same issue here. Issues with accountsd since monday. Sometimes the issues disappear. But it always seems to come back after some time. Regular freezes of Safari and Spotlight.

iMac Retina 5K Late 2015 - MacOS Catalina 10.15.7

I had the same problem on my mac mini (late 2012) but my macbook (late 2013) is ok...

(I don't use mail.app, on icloud I only tagged photo synch)

I installed the combo update... same thing after reboot

When I killed the commerce process, effectively accountsd process goes back to normal (20-35%)... but I must kill it at every reboot!

I tried also to remove the sql files !... same problem after reboot

Then I removed the keychain...!

macmin:~ mr$ ls Library/Keychains/

1243C06C-4468-55F2-99F5-52BA47B6FB03 login.keychain metadata.keychain

Microsoft_Intermediate_Certificates login.keychain-db metadata.keychain-db

macmin:~ mr$ sudo rm -rf Library/Keychains/1243C06C-4468-55F2-99F5-52BA47B6FB03

crazy !!!

since two reboots it seems ok now... but for how long?

marcel

Hi!

I had the same issue and i contacted apple support via phone.

The guy was very sweet and helped a lot.

What he recommended was to remove the apple ID (and other internet accounts) and add them via safe boot (turn off your mac then press left shift and power button, keep holding shift but releasing the power button until your login screen appears). Then just add your accounts in the system preferences --> internet accounts AND apple ID (in the apple ID icon)

Hope it helps :)

P.s: Apparently it was a processes conflict

Same here: MacMini 2018, Catalina 10.15.7 update, Mac unusable because aof accountsd eating CPU...

What I tried: disable icloud, disabkle google account, install combo update. All of this brings one day of normal work. The next day accountsd is up again on > 500% CPU.

APPPLE come on!!! Please read your paying customers' feeds and fix this!

2 days ago I had this issue and installed the Combo Update mentioned a few times on this post. Today I had again this problem and solved it by doing what you said, closed my Apple ID session, restart holding left shift, login again my Apple ID and then restarting.

Hope this time it stays longer! but Apple needs to fix this ASAP before Macs start burning out all over the world... maybe is what they want so everybody moves to new ARM devices.... like when you iPhone suddenly starts bugging just after a new iPhone is presented to the market

Same issue here on a 2017 iMac. Issue started post upgrade to 10.15.7, before that was completely fine. Logging out of my Apple ID "fixes" the issue, but as soon as I log back in the CPU spikes back up again due to accountsd.

I had the same issue. Fan running insane and using 260% CPU.

Reboot in Safe Mode - then shut down and reboot again in the normal way.

The fan spinner for at short time. Probably because the Mac was hot, but now after a few minutes it's gone.

Hope it will help other users.

I did not du the combo install, but just let it run, only took about 1.5-2 hours for my MacBook Pro from 2019, where I did not use its how ever it did peak around 700 % usage, but since then it has not have any problems.

I've had the same issue a couple of times over the past week. Signing my Apple ID out and rebooting has fixed it, but it has come back again later. First time things were good for a few days, the next few times the problem came back immediately after signing in again with my Apple ID.

It think the cause has been the recent outages that Microsoft has had with their Exchange servers worldwide over the past week or so - my having problems have coincided with those outages. Perhaps the Mac has been getting an unexpected response from Microsoft's servers during these outages, and Apple has a problem with their error handling code?

Is anyone at Apple actually following this thread?

It has 17K views... A Google search of pages containing both Accountsd and CPU returns 60.000 hits... I would be worried by now. On topic: I've logged out of iCloud on my Macbook pro 16" until this problem gets the attention from Apple that it deserves. So fat the CPU is behaving OK.

Exact same thing here, using MacBook Pro 16” 1019. Logging out of iCloud and logging back in solved the problem, but only temporarily. Booting the next day triggered the same problem. I then simply restarted the system and that seemed to take care of the problem, but I am not holding my breath...

EDIT to my previous message:

The issue is not permanently fixed by using OnyX. The only solution I see is to log out of Apple ID and not log back in again.

If you want to log back in, after you do so you can go to "~/Library/Accounts" and rename Accounts4.sqlite to something like

Accounts4.sqlite.backup

This solves the issue but it could break iCloud sync or do strange things with your iCloud Drive so I do not suggest to do that.

I think it's better to live without Apple ID until Apple fixes the issue than to take the risk.

Hi

Brand new iMac 2020 running Catalina!!! Same issue here as I'm typing this (1 Oct 2020). CPU heating to 100 degrees celsius!! I installed the latest Catalina update 10.15.7 and the issue persists. The fans run full speed (hence noisy!) and in order not to fry my expensive iMac I discovered that if I force quit (via activity monitor) the process "commerce" it automatically kills the process "accountsd"....then the %CPU goes to normal values and the CPU temperatures go to normal values <50 degrees celsius. It can happen that the commerce process comes back again depending on what I do (seems related to when I'm signing in to my apple account)....and then I get again the CPUs burning again.

@APPLE: I find this unacceptable! Such an expensive machine becomes good for boiling water! Please solve this ASAP! Thanks! For the rest I'm happy with the iMac but guys I did not buy such an expensive computer to see it fry its own CPUs due to some weird bug!! Please let me know when you have this solved. Thanks!

to be honest, i don't think Apple or someone from Support is reading here. i'm pi**ed off, really...can't work in a proper way...

we should all call the support and tell them to check this post, or send them mail or something else.