If you are like me, you might be working on the Mac with dozens of windows open at the same time, yet trying to use the computer’s memory in the most economical way given the needs. As an application developer and a WordPress techie who spends most of his time working in and switching between the web browser windows, my IDE, database tools (especially Navicat), and the command line. Also I occasionally use a few applications from the Adobe Creative Cloud suite of products.
Once any Adobe application from the Creative Cloud suite is installed on a computer, Adobe first sets up a set of its mixture (or a hybrid) of ‘agent’ and ‘installation manager’ applications on the system, whose resources they could be consuming extravagantly. These little Adobe CC agent apps are always running and strutting around behind the scenes with GUI-less interfaces, even when you are not using a single Adobe application. And they are only noticeable from the list of background tasks and software daemons. To make things worse, they can be wasting a lot of your CPU time if not also a considerable amount of RAM.
In the first times, I personally did not care much about it, as I thought just hitting the Adobe CC icon (which resembles an infinity symbol) in the menu bar, and then quitting Adobe Creative Cloud from there would just shut it up, and reclaim all the memory and CPU it had been consuming.
Secret Agents also known as UNIX daemons Working in the Background
Adobe Creative Cloud software has a number of undercover agents always running in the background, apparently doing certain deeds of Adobe, even after quitting the application from the menu bar, or even when there is no single Adobe application that is active(ly running in the foreground) or one that you have ever launched. In fact, I have recently come to the realization that quitting Adobe Creative Cloud from the macOS menu bar does not really quit anything except removing its icon from where you last clicked it (in this case, the menu bar).
This can be clearly observed by watching them under-the-hood with the Mac’s Activity Monitor, or more conveniently with the command line bash utility from within the Terminal application.