coreaudiod and launchd 100% monopolizing CPU All the Time

Have tried a few solutions suggested on this and it's simply unexplainable. Per Activity Monitor my CPU usage is at a constant 100% between coreaudiod and launchd and higher if any other app is opened. Yep, this is with everything OFF. CPU Time is always more than 2-3 hours and Idle Wake Ups can bounce up to 1,000,000 or higher. I have reinstalled Mojave 2x. No resolution. I have found an item about recreating the Audio Preferences folder that was/is missing in the HD directory Preferences Folder. No resolution. I have searched for background processes - found none. Does Anyone have familiarity with this issue who might be able to walk me through what's going on here?


I maintain a legacy editing app on Mojave, so this is on a Mac Mini 2018. The user account was migrated from an older Mini a couple of years ago, though do not recall seeing THIS issue - til this week. I've changed Permissions, I've tried Safe Boot to rule out extensions. No change in that mode. Could someone advise on at least where the components of core audio "should" be found, so I could check that ? It seems core audio is just in a constant state of pinging something - and it's giving my fans and memory a workout...like continuously amping up, and with heat.


Totally stumped on this and Apple Support did not offer any help. Do they not simply no longer advise on any issues if someone has an older OS? Even if i have to pay for Apple Support? Thanks. Really don't know what to do and need this for work.

Mac mini, macOS 10.14

Posted on Nov 2, 2023 10:09 AM

Reply

Similar questions

15 replies

Nov 2, 2023 10:38 AM in response to MIKEinMICH

Download and run this little "discovery" utility, Etrecheck. It takes a look around your Mac from the inside. It fixes NOTHING! its sole purpose is to generate a report that can be used to see what is happening.


If you follow the instruction precisely, a pre-sanitized (of any personally-identifiable information) report can be 'Shared' to the Clipboard, then posted to the forums using the 'Additional Text' icon in the reply footer online.

Nov 3, 2023 7:22 AM in response to MIKEinMICH

T


hat folder is NOT in the right place.


~/Library/Preferences/Audio


the folder in the procedure is in YOUR Userid folder, and you have omitted to absolutely essential tilde[~] on the beginning, whcoih would place it in the library of 'Current User'.


You have instead cited a folder in the main system Library folder, which is not what is needed.


when correctly placed, that folder will show in


YourBootDrive/Users/YourUsername/Library/Preferences

Nov 2, 2023 1:51 PM in response to Grant Bennet-Alder

Readers here love MalwareBytes for its ability to scan ON DEMAND. But we do not love it seeing it running at all times, punishing performance while it does the same work it already did, over and over and over.


You should set it to scan ONLY on demand, or remove it entirely.


you have some sort of App deleter. there is no place for such stuff on your Mac. you= should be using the App maker;s un-installer, not that name-guesser:


User Login Items:

  [Not Loaded] AppCleaner SmartDelete (Julien Ramseier - installed 2023-11-01)

    Modern Login Item

    /Applications/AppCleaner.app/Contents/Library/LoginItems/AppCleaner SmartDelete.app

Nov 2, 2023 2:01 PM in response to Grant Bennet-Alder

you appear to be running a Bit Torrent app. While these can be great for obtaining certain things, they also mean your Mac is an active SOURCE for fragments of files shared with others. Time for that to GO.


These are all obsolete, and should be removed:


Ssilverlight

Flip4Mac

Perian


Disk warrior is obsolete, and now that drives cost pocket-money instead of 'mortgage your house' money, 'Best Practice' is to be running Time machine, or RELIGIOUSLY adhering to a backup schedule.


After that, is there still a compelling reason to have System Integrity Protection disabled? it should be enabled to protect your Mac.

Nov 3, 2023 8:54 AM in response to MIKEinMICH

I truly have NO IDEA what is supposed to be where, only that, according to the script directions you posted, the important items will be in the ~/Library folder (under your User-id), not in the main /Library folder, based solely on the directions you said you found somewhere. Have you done a Restart since you created those folders?


I see no point in deleting, then recreating the same thing, provided you and Admin appear to be able to read and write the folder in ~/Library , which does appear to be true.


those two items in the main /Library/Audio folder seem to be related to system settings, like overall Volume level and connected hardware. I have them on my Macs as well.


on my Macs, that do not do any substantial audio creation, I do not have ~/Library/Preferences/Audio folder.

I DO have ~/Library/Audio folder , and it has several folders including Plug-ins folder inside.


~/Library/Audio folder has Me: read/write and everyone no access. It might be interesting (and unlikely to cause any damage) to add Admin:read/write as well.

Nov 2, 2023 1:17 PM in response to Grant Bennet-Alder


This is the Etre Check report in "Additional Text" pursuant to my statement of the problem above. If not, I'll try again. FWIW, It doesn't appear to find any issue or suggest anything that addresses this but this seems an obscure issue and based on trying "solutions" I've read each effort has not resolved the problem but maybe there's something that stands out in this report. Thanks


Nov 2, 2023 1:42 PM in response to MIKEinMICH

that's perfect.


you have a Bunch of stuff that is certied antiques, and features in MacOS that may be disabled because of them.


Tops on my list is TRIM. you have the VERY obsolete Cindori Trim Enabler package installed and it should go. Once it is gone, turn on TRIM for MacOS third-party devices with the Terminal trimforce command:


sudo trimforce enable


https://www.lifewire.com/enable-trim-for-ssd-in-os-x-yosemite-2260789

Nov 2, 2023 3:03 PM in response to Grant Bennet-Alder

Thanks, I will definitely try and get all that out. Meantime though, if the CPU coreaudiod issue persists, I wonder if you have any ideas on what could be going on... and I'm posting the solution I'd hoped would resolve it since what was described there is basically identical to the issues I'm encountering (and others have ) and I did indeed migrate this machine's user profile over from the previous Mini when I moved from a '12 to an '18 unit....upgrading then to Mojave. It sure seems coreaudiod is 'seeking' something continuously - like a prefs folder that's in the wrong volume. The explanation in the suggested solution is quite logical but i tried it multiple times now and so far no change... :(

Nov 3, 2023 7:01 AM in response to Grant Bennet-Alder

Ok, the folder in question exists, as shown in the screen shots below. Yes, I've done the restart since creating the folder. The problem persists.


I don't know if in fact anything else, specific to the coreaudiod is supposed to appear in that Audio folder other than the .plists indicated, but as you can see it does not.


As to specifically what/where the elements of the coreaudiod are and, should normally be found, I'm not sure. CoreAudio is being recognized by my devices from "somewhere" : ) -- But the CPU issue is unresolved. I've included a third screen shot. This indicates one of the Activity Monitor's views from a few minutes ago. Note the Idle Wake Ups. Clearly, it is specifically the coreaudiod and launchd processing that is totally consuming the CPU.





Nov 3, 2023 9:33 AM in response to Grant Bennet-Alder

Thanks for that info. So, once again upon following the directions I found for a solution, and recreation of the ~/Library/Preferences/Audio folder, including adding/enabling Admin and User permissions i.e., read/write priveleges - and yes, Restart... once again, there is no resolution of the problem --zero impact on the high % CPU readings in Activity Monitor.


It is also maybe notable, that the ~/Library/Audio preferences folder is empty. Nothing "populates" it when I do the terminal commands routine described, to recreate. So I'm kind of still at square one on this. Quite vexing.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

coreaudiod and launchd 100% monopolizing CPU All the Time

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.