This is a re-post of a previous query. I used a misnomer while describing the problem the first time, so it's no wonder no one could give me an answer. Apologies.
I called it (incorrectly) the "Adobe Resource Manager". The correct name is "Adobe Resource Synchronizer".
While working in Adobe, I notice that my computer starts to work very hard -- the fan becomes loud. I open up the Activity Monitor and see that Adobe Resource Synchroniser is using a huge amount of the system resources -- sometimes over 95%! I quit the program and the fan calms down again. This happens every time I have Adobe Creative Suite 5.5 open.
I'm sure this is not normal behavior. Could anyone tell me how to fix the problem?
I see the same issue. I removed it as an auto-start option, but it still starts up for some reason. When it runs it takes up 80% or more of the CPU resources, forces my cooling fans to kick on and suck battery life in a big way. I can kill it, but it starts back up. How do I remove this crap once and for all?
The image below shows the difference between having Adobe Resource Synchronizer running and right after force quitting it.
I am not sure either why it needs to run, or when it triggers.
I quit out of all Adobe apps. Then quit ARS, then I opened each CS5 app separately, ID, PS, AI, Bridge, then Acrobat Pro X. So far the ARS has not started up.
I have investigated and found this is a function of Adobe Acrobat and it is used to check the status of any Tracker items in Acrobat Pro (reviews or forms). It is supposed to check in every so often, then I would assume after that it should shut itself down. However, it is obvious that it doesn't quit on its own. Another function of a corrupted Acrobat preference file perhaps? I have noticed that Acrobat preferences corrupt very regularly, especially if you are active in putting interactivity into PDFs.
You can turn off the occasional checking in of AdobeResourceSynchronizer.app in Acrobat and Reader's Tracker prefs. And if it won't turn off on it's own, perhaps trashing Acrobat's prefs files might help.