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: By global modules will not be loaded, I mean the global modules node. Can you also take a look in solution explorer, it will probably be empty and you should see errors in the npm output pane. So you're saying many npm ls -g processes start spawning after this?
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: By global modules will not be loaded, I mean the global modules node. Can you also take a look in solution explorer, it will probably be empty and you should see errors in the npm output pane. So you're saying many npm ls -g processes start spawning after this?