Creative Cloud Core Service high CPU usage

@carey_1976 

did you check your background processes?

info: https://helpx.adobe.com/x-productkb/global/adobe-background-processes.html

update: https://community.adobe.com/t5/creative-cloud-desktop-discussions/adobe-background-processes/m-p/14243032

I'm having the same issue on Sequoia. Couldn't figure out why my battery started draining all the time, then realized it started right after I bought CC. Looked in activity monitor and its running at 90 something percent, even when all Adobe apps are closed.  Software that drains my battery this way is unusable and should be returnable.

Thanks for uploading the log file @DStahlnecker . We'll take a look and get back to you.

I've been having this problem. I've uploaded the log file. Filename is: AdobeLogs_20241012_213526_915-mac-GS.zxp

Hi @vbamoipdsop . When the problem occurs, could you collect and upload a log file and share the full uploaded log file name in this thread? We'll be able to pull the logs on the backend and investigate why you're running into this. Details on how to create and upload the log file are available here: https://helpx.adobe.com/creative-cloud/kb/cc-log-collector.html

this is a sporadic problem affecting relatively few users.  ntl, your poont is noted

September 2024 and this issue is still affecting people. How is it possible that an installer helper can be so poorly coded?

Can we please have this addressed in an update as a matter of urgency. It doesn't make sense that any application has to burn through multiple batteries, before something is detected as going wrong, let alone forcing the user to go in and press a command key or even reinstall the Installer. It is completely absurd. The only reason adobe gets away with this is because they have a monopoly.

if you stop file syncing, does that stop the 100% cpu utilization?

I have the same issue as others here. It's a fresh install on a brand-new installation of Sonoma. The Creative Cloud Core Service consistently sits at 100% CPU usage, with the fans going full blast. I can quit the Core Service through Activity Monitor or the Terminal, and that solves the issue. Definitely a current problem with the program.