93

I've recently updated VS2013 to Update 1 and since then VS takes CPU usage to 25% (on a 4 cores intel i5 cpu) permanently even though it's supposed to be idle. I thought it has some unfinished background processes so I left it running for a while but it keeps using the cpu when it's supposed to be idle.

Are you getting a similar behaviour after updating?

Edit 1: I'm using git and python tools for vs, so there might be some conflicts after Update 1.

Edit 2: The git integration in VS2013 is buggy. I ran a profiler on devenv.exe and git2-msvstfs.dll takes most of cpu usage although it should be idle. I sent a failure notice to MS. If you have the same problem please vote for this: http://connect.microsoft.com/VisualStudio/feedback/details/844616/vs2013-update-1-cpu-usage-not-normal

enter image description here

Edit 3: Update 2 has been recently released. This bug was fixed in VS2013 Update 2.

Edit 4: Updates 3 & 4 were released and CPU usage goes crazy due to multiple causes (not only git dll module). Disabling Browser Link as in one of the below answers seems to fix the problem.

remus
  • 2,635
  • 2
  • 21
  • 46

6 Answers6

199

For me (VS 2013 update 4) the solution was to disable Browser Link as specified here:

https://www.devexpress.com/Support/Center/Question/Details/T102322

enter image description here

The CPU slowed down right away from 25 % to 1 %.

zukanta
  • 2,691
  • 2
  • 19
  • 25
  • I think this is another bug, unrelated to the git integration bug. As you can see from my screenshot: the CPU load is due to git2-...dll I'm using VS for C/C++ development and the browser link is not even activated for C/C++ development. – remus Dec 03 '14 at 14:28
  • this worked for me as well - VS2013 + Update 4. Thanks! – abjbhat Dec 15 '14 at 10:29
  • This fixed my issue as well. Just a guess, i think VS goes haywire due to the Chrome browser spawning up seperate processes for each tab. – Fixer Dec 25 '14 at 15:21
  • I think what made this issue worse for me was I have my IIS running even after I stop debugging, this fix seems to work. – crabCRUSHERclamCOLLECTOR Jan 07 '15 at 19:31
  • That indeed fixed it! Thank you so much! – Asbjørn Ulsberg Jan 12 '15 at 20:12
  • 2
    Thanks, this solved my few weeks of suffering. CPU was at 40% 30 minutes after I opened one big web solution. Even without doing anything with it. When I unticked the "Enable browser link" option CPU immediately droped to 0%. – Goran Genter Feb 03 '15 at 10:47
  • 4
    Thanks! Fixed it for me too on Surface Pro 3. It was sitting at 43% cpu utilization when idle. Went to 0% after disabled. Even when running the site on IIS completely and without attaching to process. I suspect it is also interfering with Chrome -> Inspect Element, where you get a massive lag. – Ales Potocnik Hahonina Feb 19 '15 at 15:21
  • 2
    This worked for me as well, but took a restart of each Visual Studio instance that was running to take effect. Thanks! – KJ3 Feb 24 '15 at 20:24
  • Thanks, had same issue and this just works on VS2013 U4. – Fabio Carello Mar 30 '15 at 12:55
  • woow, that was magically, dropped processor VS processor from 47% to 0.5% and the Computer processing from freezing 100% to 11% – Bishoy Hanna Jul 10 '15 at 05:05
48

Edit 2: Possible bug regression in Updates 3 & 4.

Edit 1: The bug was fixed in VS2013 Update 2.

One can disable git plug-in from Visual Studio 2013 in this way:

Tools->Options

Source Control: set Current source control plug-in to None

Use other git clients to manage your repositories.

Community
  • 1
  • 1
remus
  • 2,635
  • 2
  • 21
  • 46
  • 2
    I have this same issue using `Visual Studio 2013 Update 2` with ***Current source control plug-in*** set to ***None*** – Clint Powell Jul 04 '14 at 17:11
  • same here! the problem is related with something else. – andresp Jul 14 '14 at 19:11
  • @andresp Can you run a profiler on devenv.exe for a few minutes and see what's using the cpu? (As I did in Edit 2) – remus Jul 15 '14 at 07:39
  • 3
    You can find the profiler in Analyze->Profiler and Attach it to another instance of devenv.exe – remus Jul 15 '14 at 07:52
  • 3
    I'm running Update 3 and had high CPU usage until I disabled the Git source control plugin; CPU dropped instantly. Possible regression? – Thorarin Sep 23 '14 at 14:12
  • @Thorarin Could be. I haven't updated yet but I gave up using git in VS. There are a lot better tools than the basic git module from VS, e.g. SourceTree from Atlassian. – remus Sep 23 '14 at 15:22
  • Thanks, this fixed the 100% of one core usage by VS2013 update 4 on my Win7 system. Laptop had been screaming at me for weeks. – Nathan Kidd Jan 17 '15 at 02:01
  • 1
    This problem happened for me after I installed the 3rd party GIT tools and setting the plugin to None fixed it. Interestingly, after setting this to None, I have set it back to the MS Git provider and the problem has not returned. – TreeAndLeaf Jul 17 '15 at 00:10
  • Although this worked for me, it means I have to do without the history and code annotation features. Not good. – Ciaran Gallagher Apr 11 '17 at 09:25
0

We fixed it by opening the VS in SafeMode. Add / SafeMode to the initiator.

MarckSi
  • 31
  • 5
  • 16
    You shouldn't use VS in SafeMode. Many functionalities are disabled in SafeMode. – remus Dec 03 '14 at 14:29
  • If safemode alleviates the problem you should take a look at the extensions you are running as safemode disables all of them. – Ralph Feb 08 '16 at 22:07
0

In my case, it was the inclusion of References to the solution that caused the high CPU usage. The project was an IronPython package that also used some DLLs. Adding the DLLs to the References was fine. The first time that a DLL was opened in the Object Browser then CPU hit 25% (1 core) and stayed there. Deleting all the References returned the CPU to normal again.

Yet Another Solution: Delete any objects under the project References.

(VS2013, Update 5, with Python Tools 2.2)

scottinthebox
  • 31
  • 3
0

In my case, I normally run several copies of Visual Studio at the same time. I've found, if I start the 2nd (or 3rd) copy of Visual Studio BEFORE the 1st (or 2nd) copy has completely loaded and settled down, I get a DEVENV stuck at 100% CPU no matter what I do after that. I have to close all copies, and open again.

I hope this helps someone, it was driving me nuts.

Billy

Billy Willoughby
  • 806
  • 11
  • 15
0

Had a similar problem with vs2015 - deleting the .suo solution file fixed it for me so far.

john blair
  • 466
  • 5
  • 13