Mac Creative Cloud desktop doesn't really quit when choosing the "quit" option

[Brock Brandenberg]

What part of "quit" do the Adobe Creative Cloud desktop app developer(s) not understand? When the user chooses the "quit" option in the modal dialog after choosing "Quit" from the file menu, the user expects the "Creative Cloud" process to completely stop and no longer consume CPU resources. But for some stupid reason, the app process continues facelessly and chews up 2%-4% CPU on my i9 laptop which is not insignificant when it's on battery power and I'm not doing a single damned thing with any Adobe app.

I expect this behavior when choosing the "hide" option when quitting (just typing that makes it sound even more stupid on Adobe's part), or I can understand some other daemon processes continuing to run, but the main "Creative Cloud" process that is the app should quit without question. If I then re-run the desktop app, it hangs, reports in Activity Monitor as "stopped responding" and chews up even more resources 😕 So I'm quite sure that one of your nine thousand unnecessary background processes is hung up or doing something wrong in this day and age of absolutely overcomplicated bloated crapware.

[kglad]

here's info on the background processes, https://helpx.adobe.com/x-productkb/global/adobe-background-processes.html

you can terminate what you want manually using activity monitor (mac) or task manager (win).

and you can make suggestions to adobe here, for applicable apps, use https://helpx.adobe.com/ie/x-productkb/global/how-to-user-voice.html for others, use https://www.adobe.com/products/wishform.html

[Brock Brandenberg]

Hi kglad.

"Creative Cloud is responsible for the user interface of the Creative Cloud desktop app."

That's the process that won't quit when choosing the "quit" option instead of "hide". The window closes and the status bar item disappears when choosing "quit" so it is terminating the UI, but it is not terminating the app process which continues to use resources. The clue to something is going wrong is that relaunching the desktop app  results in it hanging (stopped reposnding), so it's definietly doing something wrong. And using the uninstaller to repair the desktop app doesn't change the situation.

[kglad]

i understand.  this is nothing new about adobe. 

adobe products have always (afaik) been notorious for utilizing, difficult to impossible for users to control, resources, and for spreading (impossible to control) installation files all over users' computers.

[Kalvyn Rasquinha]

Hi @Brock Brandenberg . The behavior you're observing about the "Creative Cloud" process not quitting is not the expected behavior. Could you collect a log file ("Help > Create log file" from the app for instructions) and share the zxp file with me so we can investigate what's going on?

[Brock Brandenberg]

I'm happy to. I have run the Log Collector, generated the .zxp file, and uploaded it to the portal. The email response was:

The following file has been uploaded on Adobe LogCollector Portal:

File: AdobeLogs_20221209_133101_742-mac-GS.zxp

One unique aspect of my machine is that I run with my home folder located on a different volume than the boot volume (or volumes in the case of the new isolated data volume). As a long-time developer, it's been far easier to work with mutliple OS versions installed when my home folder does not reside on the boot volume and therefore does not need to be duplicated among the OS versions. The redirection is done solely using the "Home directory" path in the advanced options of the User & Groups sys pref pane. I mention this because it's far too easy for a dev to assume fixed paths instead of properly using the system APIs to determine certain folder locations. Not that folder locations is the issue here, but it is a unique aspect of a relocated home folder.

[Kalvyn Rasquinha · Accepted solution]

Thanks for sharing the logs - very helpful! This bug will get fixed in the next release of the Creative Cloud app (version 5.10).

[Brock Brandenberg]

Thanks Kalvyn 🙂