

#MOVIST HOGGING CPU ON MAC HOW TO#
How to fix accountsd CPU usage?Īffected users have offered a wide range of potential solutions, but your mileage may vary. If no account for a particular service exists in the user's Accounts database, you can let them create and save an account from within your app. Instead, the user grants your app access to use their account login credentials, bypassing the need to type their username and password. When you integrate the Accounts framework into your app, you don't need to store account logins yourself.

An account stores the login credentials of a particular service, such as Twitter, and you use those credentials to authenticate with the service. The Accounts framework provides access to user accounts stored in the Accounts database, which is managed by the system. Apple's developer documentation says this framework helps users access and manage their external accounts from within apps, without requiring them to enter login credentials. What is accountsd?Īccountsd is a daemon, part of the Accounts framework. While this issue has popped up occasionally over the years, there has been a noticeable uptick in complaints across the Apple Support Communities, MacRumors Forums, Twitter, Reddit, Stack Exchange, and elsewhere since the release of macOS Catalina version 10.15.7, with users attempting to troubleshoot the issue. One user in the Apple Support Communities shared a screenshot of "accountsd" with CPU usage above 400%, rendering their 2018 MacBook Pro "useless." Following the release of macOS Catalina version 10.15.7, an increasing number of users have experienced an issue with a system process named " accountsd" showing very high CPU usage in Activity Monitor, causing their Mac to slow down.
