Accountsd: How to Fix High CPU Usage on Mac
An growing number of users have encountered a problem with a device process called "accountsd" following the release of macOS Catalina version 10.15.7, which shows very high Processor consumption in the Activity Monitor, causing their Mac to slow down.
"One user posted a screenshot of" accountsd "with CPU utilisation over 400% in the Apple Support Communities , making their 2018 MacBook Pro" useless.
Although this problem has arisen periodically over the years, since the release of macOS Catalina version 10.15.7, there has been a significant increase in feedback around the Apple Support Communities, MacRumors Forums, Twitter, Reddit, Stack Exchange, and elsewhere, with users seeking to solve the problem.
What is accountsd?
A daemon, part of the Accounts system, is Accountsd. The developer documentation from Apple says this arrangement enables users to access and control their external accounts from inside apps, without needing them to enter login credentials.
The Accounts structure gives access to user accounts stored in the system-managed Accounts database. An account stores a specific service's login credentials, such as Twitter, and you use those credentials to authenticate with that service. You don't need to store account logins yourself when incorporating the Accounts framework into your software. Instead, the user grants access to your application to use their login credentials for their account, bypassing the need to enter their username and password. If there is no account in the Accounts database of a user for a specific service, you can let them build and save an account from inside your app.
How to fix accountsd CPU usage?
Affected users have offered a wide range of potential solutions, but your mileage may vary.
Some users have managed to solve the issue by signing out of their Apple ID account under System Preferences > Apple ID > Overview > Sign Out, restarting their Mac, and then signing back in to the account, but this has not worked for everyone.
Some users have solved the issue by resetting their Mac's SMC and/or NVRAM.
One Stack Exchange consumer thinks the problem relates to a file indexing bug on the Mac. Their workaround is to reset the indexing by navigating to Device Preferences > Spotlight > Privacy and adding (+) your storage drive ("Macintosh HD" by default) to the list "Prevent Spotlight from searching for these locations." Then delete-) (the drive from the list, and reindexing will begin on your Mac. The indexing process will briefly slow down your Mac, so compatibility with these steps is recommended.
Some users have succeeded in navigating to "~/Library / Accounts" and renaming the file "Accounts4.sqlite" to "Accounts4.sqlite.testbackup" or using more complicated terminal commands for more advanced troubleshooting, but proceed with caution, as these solutions may affect your iCloud accounts or synchronisation.
This dilemma has yet to be recognised by Apple. We will update this article accordingly should a software update be published with a patch.
Comments
Post a Comment