Skip to main content
Participant
November 29, 2017
Question

Adobe CC Desktop App takes up 100% CPU

  • November 29, 2017
  • 4 replies
  • 3270 views

Right after installing the CC Desktop App, the CPU utilization had waves of 100% usage, which makes the server unusable:

T3p7u2l.png

The main processes are those:

M50Oo68.png

For sake of future searches, I am putting the names of the processes in writing:

Adobe IPC Broker

Node.js Server-Side JavaScript (appearing twice)

Core Sync

Adobe CEF Helper

Creative Cloud

One solution I read spoke about renaming the node.exe file, but that did not improve the situation for me.

The only 'solution' that worked for me was:

- Install the Desktop App

- Install Adobe InDesign Server CC2017 and license it (that is the only application I needed on that specific machine)

- Tell the Desktop App to not load at start up, and then quit it

It will not solve the problem completely, but at least the CPU usage spikes are very short, which make the server -finally- usable.

I uninstalled everything, and deleted the following folders before re-installing, and it made no difference:

C:\Program Files (x86)\Adobe

C:\Program Files (x86)\Common Files\Adobe

C:\Users\<user_name>\AppData\Local\Adobe

C:\ProgramData\Adobe

Answers to common questions:

- The server does have an outgoing internet connection (no proxy defined)

- Other installations on the same sub-net did not show this behavior

- The issue starts right after installing the Desktop App, and before doing anything else

- I disabled the auto-update to Desktop App

- Uninstalling and re-installing did not solve the issue

- I am using the most updated downloadable installer from the Adobe web site (link)

I doubt that there will actually be a solution to this matter. I just thought that this information might be useful for other users.

Cheers!

Dotan

This topic has been closed for replies.

4 replies

Participant
July 30, 2018

Malenky, did you happen to find the reason and perhaps a solution for this matter?

It has been popping up on various systems, without any seeming correlation.

Participant
July 30, 2018

Attempted to install on another 2016 windows server... same problem. The only solution we found was to install the adobe software needed, then uninstall the CC Desktop app. Without CC Desktop, the OS consumes an average of 7% CPU, so for some reason CC was taking up 92-93% of CPU.

We never did find out why this was happening, but like I said, after uninstalling the desktop app the server was happy and running smoothly.

Participant
July 30, 2018

Thank you, Malenky​!

It is a good idea, and we will probably implement it in some cases. In others, though, we also have other Adobe software that relies on the desktop app, so we still need to leave it.

Participant
May 23, 2018

I have the exact same problem with CC2017 on a 2016 win server.

We have 2 applications currently on it, the AdobeCC App Manager Tool (no CC apps installed yet), and Adobe FrameMaker14 (2017).

The only difference is our CPU doesn't spike, is constantly stays at 100%.

David__B
Adobe Employee
Adobe Employee
November 29, 2017

Hi Dotan,

Thanks for the info.

  • Is it continuing to run at 100% CPU utilization? I've seen some cases where it was running high initially but returned to normal levels after finishing its initial launch and setup processes in the background.
  • What OS and version are you using?

Thanks,

- Dave

Participant
December 3, 2017

Thank you, Dave, but sadly this is not the case. The CPU usage did not go down.


The server is Windows 2012 R2 in a configuration that is very common for us:

Windows 2012 R2

Adobe InDesign Server CC2017

Adobe Desktop App

The server has been working for a few days now (it is idle. Nobody submitted any jobs to it), and though the CPU usage is not as dramatically high as it was, it is still showing regular spikes at short intervals:

While it does make the server useful, it is still very troubling behavior.

In order to be sure that it is not some post-installation behavior that I've never seen before, I now ran the Desktop App (and the CPU is usage problematic again):

Let's see if it solves itself by tomorrow.

Bani Verma
Community Manager
Community Manager
November 29, 2017

Moving this to Adobe Creative Cloud