Adobe Desktop Service.exe and node.js too much cpu and ram

[tonyschwartz]

Seriously?  Adobe has to install and execute multiple node.js processes (a server side software product for building crummy bloated javascript websites) on my client machine to run the Adobe Creative Cloud (what I consider a background app)?  Between these and related apps, they are consuming exorbitant amounts of memory and CPU.  Do I have to run creative cloud 100% of the time?  C'mon man!  I just don't get it.  If I can't disable creative cloud, I'll have to get rid of my photoshop plan.  I would expect an app like this to take about 400KiB of ram and .0001 CPU, OR to not be required to run at all.  Terrible decision to deploy this crap to the client machine.  Adobe, can you help?  I'm seriously considering bailing on this product.

[Pomax]

A common misconception: Node.js is just a scripting engine and standard library for the JS/ECMAScript programming language, just like how python is just a scripting engine and standard library for the Python python language. Sure, you can build crummy websites with them, and you can build gorgeous websites with them, and that's entirely unrelated to either Node or Python.

As for why you're seeing it: node.js comes with CC, and is constantly running, because CC apps run quite a lot of (shared and private) functionality via API calls, and _something_ needs to service those calls. For a few years now, that something has been Node.js

And no, you don't need to have the Creative Cloud app running, you just need to run it to manage your applications. If you're on a machine with limited cpu/ram resources, turn off "launch Creative Cloud at login" in the app preferences, and remember to quit the app when you finish updating any apps through it.

[eddified_work]

I've got a fairly recent computer with a powerful i7 CPU. "Node.js Javascript Runtime", which resides on disk at "C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs\node.exe" and constantly, 24/7, eats 13-20% CPU. This is inexcusable. Yes, "something" has to serve calls, but that something does not need to use 20% CPU when at idle. I'm upset at wasting so much of my electricity on this. I have uninstalled Creative Cloud, and re-installed--and yet the issue persists. 

Also, disabling "Run Creative Cloud in the background after closing" option, and then closing creative cloud, does not stop node.exe from eating up my CPU. This is very, very bad behavior.

[kglad]

reset the cc desktop app by making sure it's in the foreground, then press:

Win: Ctrl + Alt + R
Mac: Cmd + Opt + R


if that fails, repair per https://helpx.adobe.com/download-install/kb/creative-cloud-install-stuck.html


if that fails and you have windows, open your control panel > add/remove programs > cc desktop app > repair

if that fails, uninstall using the correct uninstaller from https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html#sa_src=web-mes... and then reinstall using*


if that fails, do a clean cc install carefully following each applicable step:

uninstall every cc app including preferences per https://helpx.adobe.com/creative-cloud/help/uninstall-remove-app.html

then uninstall the cc desktop app, again using the correct uninstaller per https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html#sa_src=web-mes...

clean your computer of cc files per http://www.adobe.com/support/contact/cscleanertool.html

check for, and if available, update your os

if windows is your os, repair all ms visual c++ versions that can be repaired (use google if you don't know how to do this)

if windows is your os update your ms visual c++, if it can be updated (use google if you don't know how to do this)

restart your computer (don't skip this)

reinstall the cc desktop app using the "alternative download links" at the bottom of the page at https://helpx.adobe.com/download-install/kb/creative-cloud-desktop-app-download.html

use the desktop app to install your cc programs/trials>

if that fails, you probably have a corrupt user account. google your os and how to create a new one.