As long as I have one single Node.js project open in VS, the CPU hits 100% and stays there for prolonged periods, making the complete Windows desktop unusable.
CPU usage will eventually drop to 50%-60 for some brief periods.
This can be reproduced by simply creating any of the Node.js projects, the CPU will immediately go up.
See the following screenshot with a freshly opened instance of VS and a blank Node.js project.
Using :
* Windows 7 Enterprise (64-bit)
* Node.js 0.10.36 (64-bit), official installer from Joyent
* Visual Studio Professional 2013 Update 4
* NOT using Resharper
* Intel i5-3440M 2.70GHz, 8GB memory, standard HDD
I can also provide any further logs or details that you might require.
Thanks,
Jaume
Comments: I am having the same issue trying to add an existing node.js project to my system. I am also using the above referenced McAfee utility, which is enforced at my company and I have no control over its configuration. The project I'm trying to add is a yeoman-generated [angular-fullstack](https://github.com/DaftMonk/generator-angular-fullstack) application.
CPU usage will eventually drop to 50%-60 for some brief periods.
This can be reproduced by simply creating any of the Node.js projects, the CPU will immediately go up.
See the following screenshot with a freshly opened instance of VS and a blank Node.js project.
Using :
* Windows 7 Enterprise (64-bit)
* Node.js 0.10.36 (64-bit), official installer from Joyent
* Visual Studio Professional 2013 Update 4
* NOT using Resharper
* Intel i5-3440M 2.70GHz, 8GB memory, standard HDD
I can also provide any further logs or details that you might require.
Thanks,
Jaume
Comments: I am having the same issue trying to add an existing node.js project to my system. I am also using the above referenced McAfee utility, which is enforced at my company and I have no control over its configuration. The project I'm trying to add is a yeoman-generated [angular-fullstack](https://github.com/DaftMonk/generator-angular-fullstack) application.