Skip to main content
dTillmann
Inspiring
February 23, 2017
Question

Node.JS cause extreme latency and slowly internet

  • February 23, 2017
  • 1 reply
  • 3903 views

A few weeks ago I've been complaining to my ISP about my internet being slow. With high latency and very low speed.

We did several procedures and when I started testing the office machine I saw that it was something in it. Investigating further, I discovered that the problem is in the "Node.js: Server-side JavaScript (32-bit)" process.

I initially detected the problem only with DreamWeaver CC, so searching the subject on the internet, I saw some people saying to rename the file "node.exe" that runs the process so that it stops at once.

When doing the rename procedure (node.exe.bkp for example), it worked, the internet has returned to normal even with the softwares open. However, at some point I needed the Creative Cloud Library in Adobe Photoshop CC and I saw that the Library in all software did not conect anymore. It was not difficult to connect one thing to another.

Well, I had to rename the file "node.exe.bkp" again to "node.exe" and it all worked again, except my internet, which has the same problem quoted at the beginning of the text. I need a solution for this Adobe.

Have two workstations onf my office and only one have problem when oppen some CC software.

This topic has been closed for replies.

1 reply

kglad
Community Expert
Community Expert
February 23, 2017

if you disable file sync'ing and/or font sync'ing that should stop node.js

dTillmann
dTillmannAuthor
Inspiring
February 23, 2017

But the heart of the problem is that about 20 days ago this did not happen.

And another...

Where I find these options? In a specific software? Like a Photoshop?

Sou CEO da ZeroArts. E atuo como Publicitário / Designer Gráfico -> diegotillmann.com.br/links
kglad
Community Expert
Community Expert
February 23, 2017

the options are in the cc desktop app.

the problem is probably because something is trying to sync and is unable.  sync therefore continues to run trying to do something that's not possible because of a configuration problem or permissions problem or something else (like a firewall, av etc).