coreaudiod running at 100% CPU

Question

coreaudiod running at 100% CPU

coreaudiod is running at 100% CPU

I have several user accounts on this Mac.

After booting the Mac coreaudiod starts when I login to one particular userid. Logging out does not end the coreaudiod, it continues to run at ~100%.

I've killed coreaudiod (sudo killall coreaudiod) but it restarts immediately.

The only way I've found to end it is rebooting. coreaudiod does not resume until I login to the account that it seems to be supporting.

MacBook Air M1 running Sequoia 15.5

MacBook Air 13″, macOS 15.5

Posted on Jun 7, 2025 11:23 AM

Reply

Answer 1

Jun 7, 2025 9:49 PM in response to leroydouglas

Thanks for the help. i pulled a Sample from Activity Monitor as suggested and searched for a few key words but I'm far to lazy to actually read that data dump. It got me thinking in a different direction.

I figured there was a good chance some cache trash in Safari was responsible so I spent some time clearing out anything in the Safari Website Data that I didn't recognize. And there was plenty to toss. Then rebooted the Mac. Several hours later coreaudiod has accumulated 7 plus seconds of CPU time.

Not declaring victory yet, but it looks good.

Reply

Answer 2

leroydouglas

Level 10

207,944 points

Jun 7, 2025 11:51 AM in response to RB Connecticut

RB Connecticut wrote:

coreaudiod is running at 100% CPU

I have several user accounts on this Mac.

After booting the Mac coreaudiod starts when I login to one particular userid. Logging out does not end the coreaudiod, it continues to run at ~100%.

I've killed coreaudiod (sudo killall coreaudiod) but it restarts immediately.

The only way I've found to end it is rebooting. coreaudiod does not resume until I login to the account that it seems to be supporting.

MacBook Air M1 running Sequoia 15.5

see if there is anything here—

Why is coreaudiod and locationd using 150% CPU on Sequoia 15.4?

Why is coreaudiod and locationd using 150… - Apple Community

no insight you can run a "sample" while in the problem account and see if there is a clue there...

memory
open files and ports

Reply