Copy link to clipboard
Copied
The two processes that are making the processor run at max are CCLibrary and CCXProcess. Any idea?
This issue should be addressed by an update to the Creative Cloud app that was released yesterday.
You'll want to uninstall and reinstall the Creative Cloud app to get the 3.4.2.187 version. It won't appear as an update within the app. These would be the steps I'd recommend
1) Close all open Adobe products
2) Quit the Creative Cloud desktop app
3) Close all Adobe related processes using Activity Monitor or Task Manager, list of processes below:
Copy link to clipboard
Copied
I have the same issues after updating to the newest version "v3.4.1.181".
@Atul_Saini do you need more details?
Copy link to clipboard
Copied
Issue still persists after upgrading to CC 3.4.1.181.
Copy link to clipboard
Copied
Nothing changed here, and no update recieved yet (still showing 3.4.0.180).
CCLibrary and CCXProcess can be stopped in Activity Monitor. CCXProcess comes back after an hour or so, CCLibrary after a reboot.
Copy link to clipboard
Copied
Exact same problem here, Mac OS X 10.11.1, MacBook Air 11" (2011). I finally resorted to disabling the CCLibrary and CCXProcess apps, found in /Applications/Utilities/Adobe Creative Cloud, by removing the .app suffix from their names. This low-tech hack probably has negative consequences, but it can't be worse than having both CPU cores pegged at 99% indefinitely. After the hack, CPU usage stays near 0% when idle, and Lightroom appears to run without problems (so far).
Copy link to clipboard
Copied
Thanks for the low tech hack, I'm getting tired of having to quit them in the activity monitor.
Copy link to clipboard
Copied
as mentioned in the low-tech hack, I don't find the same folder names in Windows as specified for mac....where would I find the .app files for these hog processes in windows?
thanks............
Copy link to clipboard
Copied
I have confirmed v3.4.1.181 didn't solve the problem.
Copy link to clipboard
Copied
Same here, v3.4.1.181
I quit these two processes forcefully. I don't know if it is correct way...
Copy link to clipboard
Copied
They will re-start on their own quickly... At least the CCXProcess. Use the low-tech hack by sobamanju a couple answers above.
Copy link to clipboard
Copied
Thanks. I did his hack. I'll wait for Adobe's patch..
Copy link to clipboard
Copied
I have the same problem too since I updated Creative Cloud 10 hours ago.
My version is also 3.4.1.181.
I was using Macbook Pro and it should at least have 7 hours of battery.
But today, I was only able to work for 3 hours because my battery run out.
I thought there was something wrong on my Macbook, so, I checked Activity Monitor.
Then I found out that CCXProcess and CCLibrary are eating up CPU.
These apps are also causing continuous energy impact.
I think everybody needs immediate fix on this problem.
Hope this solves asap...
Copy link to clipboard
Copied
Same problem.
OSX 10.11.1 (Fully updated)
CC 3.4.1.181 (All other adobe apps show as updated)
Logging out of CC and back in did not fix.
Rebooting did not fix.
I have "Force quit" the two offending processes for now, and will rename them if they re-spawn on their own.
Copy link to clipboard
Copied
Hi, appreciate if anyone having the issue can send us the CCX Process log file. The log file is located at:
Copy link to clipboard
Copied
And please also send the log for CCLibraries: ~/Library/Logs/Adobe Creative Cloud Libraries/CC Library Process.log
Copy link to clipboard
Copied
I have a ~/Library/Logs/Adobe Creative Cloud Libraries/ directory, but no CC Library Process.log file.
There is a file called log.txt in that directory, but the last entry is 2 days and 8 hours ago.
Copy link to clipboard
Copied
The ~/Library/Logs/Adobe Creative Cloud Libraries/ folder only contains a "log.txt" file, dated Nov 27th, at 23:22
Here's a link to that file:
https://www.zestysoft.com/owncloud/index.php/s/NMX67yh4Vj74I25/download
Copy link to clipboard
Copied
​I have the file pathpath ~/Library/Logs/Adobe Creative Cloud Libraries/
but instead of CC Library Process.log I have log.txt
​
Copy link to clipboard
Copied
Concerning the CC Library Process.log file:
Same problem as for CCS Process.log file:
On my Mac with NO PROBLEM: the fle exists
On my Mac where the problem occurs: the file DOES NOT EXIST
Copy link to clipboard
Copied
Here's the link to my log.txt file in the Adobe CCLibraries folder: https://dl.dropboxusercontent.com/u/16676217/log.txt
Copy link to clipboard
Copied
El Captain, Retina MacBook Pro 13-inch, 3.4.1.181.
I had no ~/Library/Logs/Adobe/Adobe CCX Welcome directory.
I had renamed the CCX Process and CCLibrary files yesterday.
I replaced them just now, quit and restarted Creative Cloud, and they immediately went to ~100% CPU each.
Still no ~/Library/Logs/Adobe/Adobe CCX Welcome directory.
I created a directory called ~/Library/Logs/Adobe/Adobe CCX Welcome, and killed both CCX Process and CCLibrary in Activity Monitor.
After about 10 minutes respite, and after closing and reopening Creative Cloud and Photoshop a couple of times, CCXProcess is back at ~100% CPU. CCLibrary hasn’t reappeared yet.
The newly-created ~/Library/Logs/Adobe/Adobe CCX Welcome is still empty.
Copy link to clipboard
Copied
Thanks for your quick response. I meant ~/Library/Logs/Adobe CCX Welcome/*. Thanks for your reminder!
Thanks,
Jun
Copy link to clipboard
Copied
The ~/Library/Logs/Adobe CCX Welcome/ directory is empty.
Copy link to clipboard
Copied
OK, it seems the issue happens in the very early phase without log generated yet.
Could you please run Log Collector Tool to collect log debug information related to your installed Adobe Creative Cloud desktop software products? Just follow the instruction to get the zip file.
Copy link to clipboard
Copied
Here's the zip file from that log collector tool:
https://www.zestysoft.com/owncloud/index.php/s/AcfP89SZMo99Epy/download
Note that I renamed my file shortly after originally posting here, so there may be error messages relating to Adobe not being able to run those executables at the end of the log files for today.
Copy link to clipboard
Copied
OK, ran the log collector, now what? Where do I send it to?