Quantcast
Channel: Node.js Tools for Visual Studio
Viewing all articles
Browse latest Browse all 4630

Commented Unassigned: 100% CPU usage for very long periods (system unusable) [1791]

$
0
0
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.

![Image](http://i.imgur.com/rrapVZL.png)

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: Just to say: the 'missing: rimraf' error is being caused by 'sinopia', which I confirmed by: - uninstalling it (npm rm sinopia -g) - confirming there were no 'npm ls -g' errors - installing sinopia globally - seeing the 'missing: rimraf' error had returned We aren't using sinopia so I can forget all about it, but VS needs to handle the problem of errors from 'npm ls -g'.

Viewing all articles
Browse latest Browse all 4630

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>