Skip to main content
Dimgor
Dimgor
Participant
November 25, 2015
Answered

Creative Cloud is charging the CPU at 99% since yesterday's update

  • November 25, 2015
  • 25 replies
  • 55060 views

The two processes that are making the processor run at max are CCLibrary and CCXProcess. Any idea?

    This topic has been closed for replies.
    Correct answer David__B

    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:

    • Creative Cloud
    • Adobe CEF Helper
    • Adobe Desktop Service
    • AdobeIPCBroker
    • Adobe Installer
    • AdobeUpdateService
    • AdobeServiceInstaller
    • CreativeCloud(URIHandler)
    • AAM Updates Notifier
    • CCLibrary
    • node
    • CoreSync

    4) Remove the Creative Cloud app using the app uninstaller from here:


    Uninstall the Creative Cloud desktop app
    https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html


    5) Reboot the computer

    6) Download and reinstall the Creative Cloud app from here: https://creative.adobe.com/products/download/creative-cloud

    7) Launch and confirm the latest version is installed by checking the app preferences display version 3.4.2.187


    Hope that helps,

    - Dave

    25 replies

    Show previous replies
    D
    Davide Baroni
    Participating Frequently
    November 30, 2015

    What if I were to uninstall all CC stuff (CC Desktop, Photoshop, Lightroom, Bridge) and re-install everything from the scratch? Should I Deactivate everything first?

    I think this SHOULD replace all the folders and set them correctly... shouldn't it?

    G
    gootara_org
    Participating Frequently
    November 30, 2015

    Hi.

    As shimmyshack says, CCLibrary.app and CCXProcess.app seems to runs node.js servers.

    CCLibrary runs with 'Contents/js/server.js' script.

    CCXProcess runs with 'Contents/js/main.js' script.

    Both scripts seems to stop at 'proxy.getRootCA()'.

    This 'proxy' means 'node-ProxyResolver' module.

    'getRootCA' function of this module calls 'libProxy.SystemRootCA' function.

    And 'libProxy' is native library placed in node-ProxyResolver module named 'libProxyResolverMac'.

    Both CCLibrary and CCXProcess stopped at to call 'libProxy.SystemRootCA()' function.

    I hope this information will be of some help.

      G
      gootara_org
      Participating Frequently
      November 30, 2015

      Sorry, I forgot to write my environments.

      My Mac: Mac mini (Late 2012)

      MacOS: OS X El Capitan version 10.11.1

      Creative Cloud: 3.4.1.181

      I think this problem caused by El Capitan's new restrictions? (such as rootless feature) - Just a thought.

      D
      Davide Baroni
      Participating Frequently
      November 30, 2015

      Hmmmm, I don't think so. I didn't have the problem on El Capitan until last update of CC Desktop...

      S
      shimmyshack
      Participant
      November 30, 2015

      Adobe in its wisdom runs a node.js server with a very large and uglyfied main.js script which has quite a few jobs to do. On my machine CCXProcess goes to 100% of one CPU after loading IMS libraries.

      I didnt have time to debug main.js

      temporary fix

      rename the offending main.js file

      sudo mv '/Applications/Utilities/Adobe Creative Cloud/CCXProcess/CCXProcess.app/Contents/MacOS/../js/main.js' '/Applications/Utilities/Adobe Creative Cloud/CCXProcess/CCXProcess.app/Contents/MacOS/../js/main.jss'

      of course you will actually want to rename it back to allow Adobe to log your data to their cloud, and find out your membership status and so on.. So if they don't produce a fix I will be renaming every 2 weeks.

      rename back

      sudo mv '/Applications/Utilities/Adobe Creative Cloud/CCXProcess/CCXProcess.app/Contents/MacOS/../js/main.jss' '/Applications/Utilities/Adobe Creative Cloud/CCXProcess/CCXProcess.app/Contents/MacOS/../js/main.js'

      why does this work. When CCXProcess process tries to start it just abnormally ends with file not found. Eventually adobe will release an update. And main.js will be updated. Or if the update process relies on main.js being present.. who knows who tangled the Adobe web is, then by renaming every two weeks and manually checking for updates, you force an update. Just reboot and check for 100% CPU and if they haven't fixed it, rename to main.jss and wait another 2 weeks. Doubtless enough angry people will be reporting this for some time to come without coming up with their own solutions, so Adobe will be looking at this. we hope. At least it's not like Apple where a bug appears in userland and isn't fixed for years. haha

        phoenix_stu
        phoenix_stu
        Participating Frequently
        November 30, 2015

        Ok I am at a complete loss.  Last week I decided to buy the Creative Cloud suite and at first everything was working fine.  Libraries was a great feature. Several days ago the Libraries all of the sudden stopped working.  From that point everything went haywire.  Now it is slowing my Mac down to a near stop.  It will take all of my ram and I cannot do anything.

        Based on the information below, while I am concerned with the Library feature not working in PS, this is not a PS issue and more of a Creative Cloud issue based on the memory leaks coming from CCLibrary and CCXProcess as described below.  Although, I would really like to get my library back in PS, I would like the Memory problem to be resolved. This is why I am putting in the Creative Cloud section of the forum.

        Completed all of the solutions from the other threads here in hopes it was the Library problem as this was originally what I noticed stopped working before noticing the other issues with the Processes.

        https://forums.adobe.com/thread/1689115

        https://forums.adobe.com/thread/1748562

        https://forums.adobe.com/thread/1716069

        I have Creative Cloud 3.4.1.181

        I have looked all through the forums and tried many different things.  I have done all of the following from the other previous threads..

        1) Signed in, signed out, signed in, quit PS and then restarted -

        2) deleted the DB and OOBE files.

        3) turned everything off and back on

        4) Preferences double checked that as should be

        5) uninstalled, used cleaner tool, reinstalled. *3 times now.

        6) problem still persists so, repeated step 5 above and then reinstalled my Mac OS X

        7) reinstalled the CC and apps again and still the problem persists.

        Opened up Activity monitor and realized that CCLibrary and CCXProcess was taking 99% of my CPU. So, from the same thread from above, I quit CCLibrary from Activity and it gave me about 2Gb of Ram back.  Then the CCXProcess was hogging a bunch as well and ended up having to quit this as it was taking 5Gb of RAM!  Seriously?    Pics below.  This would only be a temporary solution as shortly it would begin to do this again.

        Don’t worry, the CCXProcess just has not caught up yet. It eventually made it to 99% shortly after the photo, but everything was so slow, it was hard to get the screen shot to start up. So I took it at the time it came up.

        The low tech hack by sobamanju is ok but, why should I have to do this?

        I ran the log tool suggested here and another thread. Just not sure where to send to. Could you please let me know where to send the log.  Thank you.

        W
        WBA3
        Participating Frequently
        December 5, 2015

        I have battled the CC 99% CPU problem for a couple of weeks and am ready to quit CC and go back to owning the apps.

        Mac Pro with OS X 10.11.1. Can't tell you CC version because I can't open it. I have killed both CC processes that run at 99% CPU and killed CC launch at Mac startup. Using LR & PS in the Dock to start them up.

        I have created an AdobeFile with the LogCollectorTool but cannot figure out how to attach it to this post. Must be a wy but I cannot find even a clue.

        Help, my trust in Adobe is almost down to zero.

        Bill

        darkcanyon
        darkcanyon
        Participating Frequently
        December 6, 2015

        For immediate result, use the cleaner tool to uninstall the CC Dekstop Click here to download Creative Cloud Cleaner tool 

        When you open the app only check to uninstall the CC Desktop app. Then reboot your computer. This helped me. Note, uninstalling the CC Desktop removes cloud synchronization and access to stock photos. I personally don't use any of that so I'm happy to permanently get rid of the app. If you use any of those services this will only be a temporary solution until the problem has been fixed by Adobe. You can install the CC Desktop app again at any time. Download Adobe Creative Cloud apps | Free Adobe Creative Cloud trial

        Also, call Adobe support and talk with them. I did that and they were very helpful.

          J
          Adobe Employee
          jun xia
          Adobe Employee
          November 29, 2015

          Hi, appreciate if anyone having the issue can send us the CCX Process log file. The log file is located at:

          • Mac: ~/Library/Logs/Adobe/Adobe CCX Welcome/CCX Process.log
          • Win: ~/AppData/Local/Adobe/CCX Welcome/Logs/CCX Process.log
          J
          Adobe Employee
          jun xia
          Adobe Employee
          November 30, 2015

          And please also send the log for CCLibraries: ~/Library/Logs/Adobe Creative Cloud Libraries/CC Library Process.log

          H
          hodd
          Participant
          November 30, 2015

          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.

          A
          Anonymous
          November 29, 2015

          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.

          M
          morizotter
          Participant
          November 28, 2015

          Same here, v3.4.1.181

          I quit these two processes forcefully. I don't know if it is correct way...

          H
          hawx2k
          Participant
          November 28, 2015

          They will re-start on their own quickly... At least the CCXProcess. Use the low-tech hack by sobamanju a couple answers above.

          M
          morizotter
          Participant
          November 28, 2015

          Thanks. I did his hack. I'll wait for Adobe's patch..

          A
          Anonymous
          November 28, 2015

          I have confirmed v3.4.1.181 didn't solve the problem.

          S
          sobamanju
          Participant
          November 28, 2015

          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).

          Gary Lum
          Gary Lum
          Known Participant
          November 28, 2015

          Thanks for the low tech hack, I'm getting tired of having to quit them in the activity monitor.

          A
          Anonymous
          November 27, 2015

          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.

          Show more replies
          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices