4 Replies Latest reply: Oct 30, 2014 3:39 PM by Stephen Franklin RSS

    Creative Cloud File Sync Memory Leak

    CuckooOrange Community Member

      Hi. The latest update for the CC file sync uses up an insane amount of ram memory (up to 1G+) when file syncing. So much so that it keeps on freezing my computer or making it so slow to be unbearable. I always have to turn off CC now or I can't use my computer.

       

      I may not have the newest computer but I have a Macbook Pro with 4G of RAM, not too bad either. The file sync should work quietly and unobtrusively in the background, like Dropbox and not hog all my memory no matter how many files I have to sync. It can probably be set so it only actively syncs a lot when it detects that the user is not using the computer.

       

      Being a paying customer, I of course wish that CC could work splendidly well. Unfortunately, I still have to rely on Dropbox because of CC's undependability and massive memory problems. The CC programs are great but honestly, so far the file sync has given me nothing but frustration. Please catch up soon.

       

      Please fix this asap so it can be usable. Thank you.

        • 1. Re: Creative Cloud File Sync Memory Leak
          David__B Employee Hosts

          Hi CuckooOrange,


          Sorry for the delay in responding. Are you still seeing the behavior? Does signing out of the Creative Cloud app and back in again make any difference (Gear icon > Preferences > Account tab in the General section)? Can you check the version from the preferences just to ensure you have the latest release, 1.5.1.369?

           

          Thanks,

           

          - Dave

          • 2. Re: Creative Cloud File Sync Memory Leak
            Stephen Franklin Community Member

            Hi David, I'm getting the same issue Core Sync is chewing up crazy amounts of memory until I run out of paging memory. Kills my machine.

             

            I'm running the lastest revision 1.8.1.451

             

            Have signed in and signed out and done a complete reinstall removing all prefs and the OOBE folder etc.

             

            I have dropped a large amount of files into the file sync CC folder which seems to forcing the memory leak. Will try removing them to see what happens.

             

            Running Yosemite

             

            Hardware Overview:

             

              Model Name: Mac Pro

              Model Identifier: MacPro3,1

              Processor Name: Quad-Core Intel Xeon

              Processor Speed: 2.8 GHz

              Number of Processors: 2

              Total Number of Cores: 8

              L2 Cache (per Processor): 12 MB

              Memory: 16 GB

              Bus Speed: 1.6 GHz

              Boot ROM Version: MP31.006C.B05

              SMC Version (system): 1.25f4

            • 3. Re: Creative Cloud File Sync Memory Leak
              jonesology Community Member

              Did this problem begin when you upgraded to Yosemite?  There are major memory leak issues that we've been trying to make Apple aware of for the past week (mainly around Mail.app); the only reason I'm responding here is because what you're describing sounds almost identical to the issues experienced with the Mail.app.  I was running Ps, Ai and Dw simultaneously (along with Bridge) during my daily workflow...I also had Mail.app open at the same time and no problems ever...until I upgraded to Yosemite. The Mail.app would suddenly race to 60 GB (yes that's sixty) of memory usage, freezing the system; I also found it was very difficult to run more than one CC app at a time, and I would have to constantly clean the memory with Memory Clean.  Are you also using Mail.app?  Could be unrelated but, this is how we troubleshoot.  Good luck.

              • 4. Re: Creative Cloud File Sync Memory Leak
                Stephen Franklin Community Member

                Sounds like a very similar problem although my issue is directly related to CC Core Sync. I had dropped some 400 MB to 1 GB GoPro files into my CC sync folder that was triggering the issue. As soon as I took them out of the sync folder, no issues at all.

                 

                Guess I was stress testing the CC Sync a bit too heavily!

                 

                sf d-)=