Visual Studio 2013/2012 Using Processor Inactivity

I am currently evaluating Visual Studio 2015 RC. I noticed that when starting the IDE, the Visual Studio 2015 process is constantly at around 25% of the CPU usage. Even without loading the project and without a welcome page, it consumes 25% of the CPU usage at a constant speed. No other applications besides background services. All other running processes use about 2-4% of the total processor volume.

This behavior has also been seen in Visual Studio 2013.

Does anyone else see this behavior? This is normal? Any suggestions?

+69
visual-studio-2013 visual-studio-2015
Jun 05 '15 at 15:39
source share
11 answers

There was the same problem. The processor is constantly at 45-50%, even when the IDE is completely free.

Turns out the problem is the Microsoft Git source code provider.

I disabled this and the processor dropped to 0 and the IDE became much more convenient.

+55
Sep 15 '15 at 0:54
source share

In my case, disabling Telerik ASP.NET MVC Extension solved a high processor problem.

High CPU utilization began with the load on the solution and did not fall (40% with one, 80% with two solutions) until VS was closed or even sometimes after (had to kill the process).

Tools-> Extensions and Updates-> Installed, find the extension and click "Disable".

+9
Mar 08 '16 at 13:10
source share

In my case, they tried to update all link counts every time I edited the code. enter image description here

I just turned them off. You can do it this way .

+3
Mar 21 '16 at 10:40
source share

You should not expect Visual Studio to digest continuous processor time.

I am starting RTM for Visual Studio 2015 Community right now when the medium-sized project is open and I donโ€™t see the processor being used continuously (according to Process Hacker 2, which shows that usage is 0.01 percent). Its just empty, which means that even 0.01% of CPU usage is recorded.

Keep in mind that IntelliSense scans your project files in the background to create a database for tooltips, etc.

Selecting Project > Rescan Solution from the menu will cause this process to be completed, which will cause the processor to be used for a while. But in the end he must calm down.

Apparently, there have always been cases where deleting Intellisense database files and fully rescan solve problems such as "odd behavior." I donโ€™t know if its a โ€œprescribedโ€ method, but if I suspect an IntelliSense problem, I just delete the .sdf file in the project folder if I want Visual Studio to start from scratch. This is not necessarily very common.

+2
Aug 29 '15 at 4:12
source share

I also had this problem, constant 20-40% CPU idling (Visual Studio 2015 update 1). I noticed that other local repositories of the same code did not have this problem.

I deleted the problem local repository and took a new check, this solved the problem for me. Why this worked, I, unfortunately, cannot explain ...

+2
Jan 12 '16 at 19:15
source share

I run resharper, disabled it and disabled the Microsoft Git provider and still had high processor problems, devenv.exe also started after closing ... until recently.

Looks like VS 2015 Update 2 resolved these issues!

https://www.visualstudio.com/en-us/news/vs2015-update2-vs.aspx

+2
Apr 16 '16 at 20:19
source share

In my case; "Visual Studio 2015 Update 1" went crazy editing JS files independent of source length. He used a high processor, and the editor even froze. I fixed the problem by disabling third-party add-ons by detecting a bug once that caused VS 2015 to fail.

Hope this works.

+1
Jan 28 '16 at 9:53 on
source share

In my case, the culprit was Node.js tools for Visual Studio . I have v1.1.2 installed, and the processor was constantly at the level of 25-40%.

Switching to Node.js Tools v1.2 RC solved the problem completely after the initial high load, which took a couple of minutes.

+1
Jun 28 '16 at 14:01
source share

In my case, it was either a roaming extension manager, or most likely a project of the role of azure worker in my solution. If you have one of them, try unloading it and restarting the visual studio. I can reproduce it, but I do not know why this is happening.

0
Mar 15 '16 at 19:39
source share

I also noticed that when starting and stopping a debugging episode on the local server, if the page is still open in the browser, VS will continue to work with a high processor. Closing the browser page stops this.

0
Apr 15 '17 at 8:09
source share

I want to share my experience. In my case, I had to change all the extensions and updates and analysis of C # code.

1 - for extensions and updates:

Tools => Extensions and Updates

2 - for code analysis

Solution explorer => right-click on the project => Properties => Click on the "Code Analysis" tab => click on "Open" bouton => Uncheck "Microsoft.CodeAnalysis.CSharp" => save and exit.

Cpu usage has been reduced to 1%.

0
Sep 07 '17 at 7:29 on
source share



All Articles