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 authored issue #1607 and have been asked to comment in here. I'm a bit limited on time so apologies for the brief response. I've been using the 'install Express 4 blank web application' method to test/reproduce the 'npm ls -g' high CPU usage problem. Long story cut short: - VS 2013.4 - Node 0.12.0 - npm 2.5.1 Here are my global modules: azure azure-cli gulp sinopia strong-build All was well with my 'new project' test until I installed strong-build and now I'm seeing continual 'npm ls -g' node.exe processes appearing. Running 'npm ls -g' shows me an error: npm ERR! missing: rimraf@~2.2.8, required by mv@2.0.3 I haven't dug into strong-build to figure out if this is an actual child/dependency but I think since the node.exe process problem appeared after installing strong-build it's quite a smoking gun. I guess my immediate question is: how is VS/NTVS handling output from 'npm ls -g' which isn't entirely successful, i.e. contains errors? Having written all of that I've now run 'npm rm strong-build' -g, and then 'npm ls -g', and I still get the same 'missing: rimraf' error. Perhaps strong-build isn't to blame, I don't know, I'll look into it further later when I have more time by: - Deleting all global packages - Installing global packages 1 at and confirming when the 'missing: rimraf' error appears. Andy
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 authored issue #1607 and have been asked to comment in here. I'm a bit limited on time so apologies for the brief response. I've been using the 'install Express 4 blank web application' method to test/reproduce the 'npm ls -g' high CPU usage problem. Long story cut short: - VS 2013.4 - Node 0.12.0 - npm 2.5.1 Here are my global modules: azure azure-cli gulp sinopia strong-build All was well with my 'new project' test until I installed strong-build and now I'm seeing continual 'npm ls -g' node.exe processes appearing. Running 'npm ls -g' shows me an error: npm ERR! missing: rimraf@~2.2.8, required by mv@2.0.3 I haven't dug into strong-build to figure out if this is an actual child/dependency but I think since the node.exe process problem appeared after installing strong-build it's quite a smoking gun. I guess my immediate question is: how is VS/NTVS handling output from 'npm ls -g' which isn't entirely successful, i.e. contains errors? Having written all of that I've now run 'npm rm strong-build' -g, and then 'npm ls -g', and I still get the same 'missing: rimraf' error. Perhaps strong-build isn't to blame, I don't know, I'll look into it further later when I have more time by: - Deleting all global packages - Installing global packages 1 at and confirming when the 'missing: rimraf' error appears. Andy