Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Node.js issue after latest update?

Community Beginner ,
Apr 15, 2016 Apr 15, 2016

yR5aXW4.png

I have the process node.exe (named 'Node.js: Server-side JavaScript (32 bit"), running on my computer, hogging a ton of CPU power. A support agent from Premiere Pro didn't believe it was part of Adobe products when I talked to them, but I believe it is part of Adobe. Look at the path:

C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCXProcess\libs\node.exe

I wasn't having this issue until Creative Cloud most recently updated, and because it's within the Adobe directory, I think here is where I need to come to get my question answered. Does anybody know what I should do? Btw, ending the task just makes it reappear a few moments later, without me doing anything to make it show up. Also, if I interact with panels within Adobe products that have my footage in them, it seems to automatically launch the node.exe program. Help!

P.S. I'm almost positive that this is related to Adobe, but if it's not.

TOPICS
Creative Cloud
10.7K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 27, 2016 Apr 27, 2016

Moving the discussion to Adobe Creative Cloud​

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 16, 2016 Nov 16, 2016

node.exe Windows process - What is it?

I had the same questions.

So I used the lookup on the taskman and got this.

------------

The process known as Evented I/O for (version V8 JavaScript)

belongs to software Node.js or BT Desktop Help or ATT Management Agent or AT&T Troubleshoot & Resolve or Adobe Photoshop (version CS6, CC 2015) or Bell Internet Check-Up or Adobe Photoshop CC or Adobe Extension Manager CC or Prey Anti-Theft or Adobe InDesign (version CC 2015, CS5) or Windstream Setup Assistant or Popcorn Time

by Joyent.

Description: Node.exe is not essential for Windows and will often cause problems. Node.exe is located in a subfolder of "C:\Program Files" or sometimes in a subfolder of C:\Windows or in a subfolder of "C:\Program Files\Common Files". Known file sizes on Windows 10/8/7/XP are 5,529,472 bytes (41% of all occurrences), 5,755,392 bytes and 11 more variants. http://www.file.net/process/node.exe.html

The program is not visible. It is not a Windows core file. The program uses ports to connect to or from a LAN or the Internet. The file is digitally signed. Node.exe is able to monitor applications and manipulate other programs. Therefore the technical security rating is 46% dangerous, however you should also read the user reviews.

.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 21, 2016 Nov 21, 2016

I have the same problem.

Here is how I solved it (the slob way) : Go to C:\Program Files\Adobe\Adobe Photoshop CC XXXX.XX\ and rename node.exe (Something like foobar.exe).

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 23, 2016 Nov 23, 2016

I have the same EXACT issue. I renamed my file. We'll see if this helps. Has it caused any problems for you - since renaming?  I also found the file in another location (C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCXProcess\libs). Once I renamed (and moved) the files, I received an error in Photoshop that a problem had been found with Generator. Apparently the file is being used to generate files on the fly, a newer feature of photoshop (2013, maybe?). I don't use that feature, so perhaps we can disable it within Photoshop.

Regardless -- once I removed those files, Photoshop returned to being very responsive.

Here is a copy of the error I have to bypass every time I open PS:

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 26, 2016 Nov 26, 2016
LATEST

Got the same problem. After renaming I see this error but at least my CPU is not using 100% of its power.
Any fix on this Adobe?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines