2

I noticed these two processes were causing my computer fan to spin right up, were using practically ALL the CPU % and they had over 40 days of CPU time clocked.

A quick Google search revealed nothing. Seems that it may be related to Apple authorization... but why would it use so much CPU??

I'm concerned because AKAuthorizationRemoteView implies it may be performing some remote view operation via Messages.

Any help appreciated.

1 Answer 1

2

akd is a background service created by Apple that runs on macOS as part of the AuthKit framework. It is used by other Apple programs to facilitate the process of validating Apple IDs.

For example when you login to iCloud from the App Store, System Preferences or similar, the akd background process is responsible for actually "talking" to Apple's servers. This approach makes it possible for Apple to centrally manage and update authentications on macOS, instead of having to bake that support into each and every app that needs it.

Note that when you log in to iCloud from a browser, akd is not involved.

Usually akd does not take up huge amounts of CPU time. The fact that it does on your computer, indicates that there was a bug in the program. For example it could be that there was some unexpected delay or break in the connection between the program and Apple's server, and that the program went into a never-ending loop waiting for something to happen.

That sort of problem is usually resolved by either "killing" (i.e. stopping) the program and letting it restart automatically, or by simply rebooting the computer.

AKAuthorizationRemoteView is part Apple's AuthKitUI framework. Similar to the purpose of AuthKit, the AuthKitUI framework contains the functionality necessary to provide a user interface for authentication with Apple's services. It is created as a framework that is shared by other applications so that Apple does not have to update each and every program when they make a change to how the user interface for authenticating with their server's look like.

The user interface would include things like a dialog for entering your Apple ID and password, dialog for entering the 6-digit 2-factor authentication codes, a password reset dialog, etc.

You do not need to be concerned about the AKAuthorizationRemoteView. "Remote View" does not mean that something or someone is remotely viewing the screen of your computer. In technical terms a "view" is something that is displayed on your display - like for example a button, a menu, a text input field or similar. A "remote view" is a view that is displayed by a different thread or process than the main process.

I.e. in this case it just means that you have a main program (Messages for example) that is using this external framework and letting it display an authentication dialog on its behalf. This dialog is then "remote" from the Messages program, although everything is contained and running on your own computer.

3
  • Great answer! Yes my concern was the amount of CPU% being utilised by this AKAuthorizationRemoteViewService and akd. I think it must have glitched or something? Can't explain why it was so long-running or why it was chewing up so much compute time.
    – sidewaiise
    Commented Feb 3, 2021 at 22:42
  • Yes, that's what I have written in my answer - the excessive CPU usage sounds like you have encountered a bug in the program. Just restart the program. It usually fixes it.
    – jksoegaard
    Commented Feb 3, 2021 at 23:28
  • I found that akd was using 250% CPU on a 4-core Macbook Pro, just after a macOS 11.6 crash caused a reboot. I was able to find this process with ps aux | sed -n '1p; /root .*akd$/p' - then noted the PID and used sudo kill -9 on that PID to kill it.
    – RichVel
    Commented Sep 10, 2022 at 12:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .