): macy:~ jens$ sudo launchctl procinfo 352Ĭom.-extension-serviceīut these aren't service which I can remove using launchctl.īased on chiggsy's answer I was able to find more traces of the service ( omitted lines marked as. Using launchctl I was able to gather more information about the service using its PID ( omitted lines marked as.
However, as mentioned before, its parent process is still launchd so I wonder how this can be. But the PID of the running ACCFinderSync process is not listed there at all. or from a third-party App that hasn't any relation to Adobe.Īlso, launchctl list lists the PID of each Label. All services on the system are by com.apple.
Unfortunately, there is no such service with an obvious name. To do so, I search for a service with adobe, accf or core*sync in its name.
#Too many adobe cef helper how to
How does Adobe get this process to be launched automatically?Īnd how to stop it from being launched automatically?Īccording to YoshiBotX's answer, I used launchctl list as well as the App launchControl to find the service that launches the Core Sync Helper. "/Applications/Utilities/Adobe Creative Cloud/CoreSync/Core Sync.app/Contents/PlugIns/ACCFinderSync.appex/Contents/MacOS/ACCFinderSync" Using the OS X activity monitor to get more information about this process it tells us that its parent process is launchd.
#Too many adobe cef helper software
You shouldnt have too many problems with CS6, or any software for that matter. Uninstall the following via the Add/Remove Panel (Start-> (Settings)->Control Panel->Add/Remove Programs) if they exist: Messenger Plus spyware. However, using this approach I got rid of all Adobe processes but one with the process name Core Sync Helper. Its an incredibly common monitor size and native resolution now. Select the following and click Kill process for each one if they are still listed (they shouldn’t be but double check it): C:Program FilesMessenger Plus 3MsgPlus.exe. It's not a bad idea to browse these directories manually just to get aware of what is - or could be configured to be - launched automatically on your machine. To get rid of this, I removed everything with "*adobe*" in the filename from the directories used by launchd, which are: ~/Library/LaunchAgents, /Library/LaunchAgents, /Library/LaunchDaemons, /System/Library/LaunchAgents, /System/Library/LaunchDaemons. I have noticed a lot of Adobe processes are running in the background at start up on an OS X 10.11.4 (15E65) machine with Adobe Creative Cloud (CC) installed.