coreaudiod and launchd consuming a high amount of CPU.
We’re an infrastructure provider first, and can only offer limited help with software issues like this one. We can’t guarantee this fix works for every case, contact Apple for further support on the underlying software. We can also provide a list of vendors we work with if you need dedicated software support.
I figured out what the problem was, in case anyone else runs into this. The Bluetooth daemon had crashed. I’m not sure why that madecoreaudiodandlaunchdgo crazy, but the fix is this:If the daemon has crashed, you may see a message like this:Next, run this:Oncebluedis running properly again,coreaudiodandlaunchdboth settle down.