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: It doesn't handle it very well :-). Currently when npm ls -g fails, it'll fail to parse the ls output and the global modules will not be loaded you will also see an error printed to the npm output pane. There's an issue on it here and a fix should be checked in soon. https://nodejstools.codeplex.com/workitem/1811. Th quick fix is to just pass the --silent flag for npm ls. However we should eventually see if we can surface these warnings better.
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: It doesn't handle it very well :-). Currently when npm ls -g fails, it'll fail to parse the ls output and the global modules will not be loaded you will also see an error printed to the npm output pane. There's an issue on it here and a fix should be checked in soon. https://nodejstools.codeplex.com/workitem/1811. Th quick fix is to just pass the --silent flag for npm ls. However we should eventually see if we can surface these warnings better.