Accountsd CPU usage high in macOS Catalina

Does anyone have contacts at Apple? Can we find the name of the person(s) who lead / are members of the OSX Mail engineering or Product Management team? We should find these folks and start writing to them directly. I live in Silicon Valley and I'm going to try to do this. I will let you all know if/when I find the names.

Just look at this thread - 22 pages of complaints and struggles! Yet NOT A WORD from Cupertino. This is ridiculous as they (Apple) also know that we don't have great alternatives to Mail. So they are free to ignore these comments / complaints / struggles. I suspect they don't even look at these pages so as they say out there "save your breath".

Please join in trying to reach Apple through other approaches as well. Thank you!

I used the link someone posted earlier to let Apple know via email that I no longer use Apple Mail on my desktop. Nothing else I can do, or am willing to do, to try to resolve the problem. I now use mail on my iPad (which has no such issue), and, occasionally, fire it up on the desktop to write an email, but I never keep it open. Problem solved. Apple absolutely knows of the issue. It is infuriating that no one at Apple is willing to respond to this thread to let us know that we’ve been heard.

I have a blog friend who has 10.15.6 and so far, tentatively, it looks far better. He's going to wait another day before reporting the results. Memory usage down, CPU stable. Fingers, toes and eyes crossed.

I have to agree with this. I've done all of these things, too. Interestingly when I switched off the "automatically manage connection settings" on the two Exchange accounts I use Mail.app crashed. Reopening it the boxes are still not checked, but accountsd and Mail are still sky high CPU use, and accountsd did not purge its memory but kept adding to it (2.6GB as I write this).

For me, what eventually drove the CPU up was memory usage and although it started small, now after three days, accounted is 405MB. Now normally after 3 days it would have been over 1 GB in size, so it's better, but it's not solved. I'll keep letting it run. I turned off a cron that I had that would kill it every day at 2am so it would stay small.

Not seeing that here, either. Been up for four days, accountsd presently at 329MB, fluctuating +/- 10%. I'd been having severe CPU usage problems with it and Mail.app prior to 10.15.6. Since the update it's been fine.

Yes, mine got to 1GB (!!) and then I had to reboot. There's still a problem. They dialed back how hard it hits the CPU, if you look at the overall CPU time used, but it's got a memory leak somewhere. No way is should be holding on to that much memory. Third largest overall!

Just for your information, I have the same cpu problem with accountsd since the last update to Catalina 10.15.7, but I DO NOT USE Apple Mail, Contacts or Calendar!!! Why is mac making intensive use of cpu when I do not use any of the possible apps which could trigger it? I guess the psicosis with gmail accounts is completely unfounded, it's a problem with apple and macos, nothing else.

After a few days OK, it seemed solved, but today the accountsd process at 300% CPU usage has come back :-(

Just in case, I've checked the suggested changes remain the same (disabled iCloud from syncing Mail and other apps data). Next step: try to uninstall any app using accountsd, or wait for next MacOS update, although I'm skeptical given the lack of new ideas to solve this issue, and the absence of Apple feedback.

Well, I upgraded to MBP 16" 8 core, did a full recovery from Time Machine and i can report that the problem is gone.

i quit using the cloud , i like keeping my files local

if you uncheck Mail, then your .mac, .me, .icloud accounts are disabled.

I installed other mail clients and activity is VERY low... so it can be fixed by Apple that owns O.S. and Mail app.

Are they gone if you use another device like phone or Mac's Safari to sign into your email account?

400% on the first account you added?

What about on the new user account I suggested a while back?