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: @mousetraps I'm actually unable to reproduce this issue since I reinstalled the plugin for the last time. If I experience it again I will try turning IntelliSense off and let you know if that alleviates the issue. In what regards to the package.json, I don't think that the structure of my project would be relevant at all. As I could reproduce the issue by creating any of the pretty much blank project templates that are added with the tool. That is with a freshly rebooted system and one single instance of VS with just the one Node.js project. Here's the output of my npm ls -g --depth=0 ├── bower@1.3.12 ├── generator-meanjs@0.1.12 ├── gulp@3.8.10 ├── karma-cli@0.0.4 ├── mean-cli@0.9.19 ├── nodemon@1.3.6 └── yo@1.3.3
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: @mousetraps I'm actually unable to reproduce this issue since I reinstalled the plugin for the last time. If I experience it again I will try turning IntelliSense off and let you know if that alleviates the issue. In what regards to the package.json, I don't think that the structure of my project would be relevant at all. As I could reproduce the issue by creating any of the pretty much blank project templates that are added with the tool. That is with a freshly rebooted system and one single instance of VS with just the one Node.js project. Here's the output of my npm ls -g --depth=0 ├── bower@1.3.12 ├── generator-meanjs@0.1.12 ├── gulp@3.8.10 ├── karma-cli@0.0.4 ├── mean-cli@0.9.19 ├── nodemon@1.3.6 └── yo@1.3.3