Anyone else seeing node.js in the Task Manger when they run Unity?

Started noticing this as well as odd behaviour by Unity exe, stalling when doing simple operations and running over budget on CPU when doing nothing?

Are you also running Visual Studio? Did you install the Node development tools with it?

VS Node dev tools I don’t think so just the Unity development tools.

I’m 99% certain that process is related to your Visual Studio install, just not exactly sure which components install it.

No don’t think so it’s running under Unity.exe in TaskManager not VS.
There is also one or two Console Window Host processes
a Unity Shader Compiler
and a UnityHelper.exe

They all startup with Unity (2017.4.0f1)?

I would expect everyone else should be seeing the same processes on startup or there is something fishy with my install?

The node.js process is most likely the integrated Local Cache Server (which is built on node.js) which starts by default since an earlier version of 2017.x.

1 Like

Also VS uses node.js internally now for stuff like syntax formatting so you will see it even with zero javascript features installed… Probably not related to this though the local cache server thing makes more sense.

1 Like

Maybe related to some or one of the services?

It doesn’t start up for me (2017.1.1f1; probably because I don’t use any Editor functionality that needs node.js), but node.js should be located under X:\Program Files\Unity\Editor\Data\Tools\nodejs.

Edit: Just checked… I still have Unity 5.3.4 installed for some reason and there’s, too, a nodejs folder under the same path (Editor\Data.…). Don’t worry, I’d say.

It’s used for the local cache server and for the Unity Package Manager.

1 Like

node.js is not a virus. It’s literally explained what it’s used for in the last post in this thread, which is from FIVE YEARS AGO