title: Visual Studio 2013 Update 2 maxes out core
body: <p>I recently installed Visual Studio 2013 Professional Update 2 on a Windows 7 virtual machine. I had been running VS 2012 with no problems, but I wanted to upgrade. Everything was working well for a week, but now for a certain project the IDE is bogging down and task manager is reporting a consistent 25% CPU usage on my 4 core machine. Restarting VS and my PC does nothing.</p>
  
  <p>If I start VS in safemode <code>devenv.exe /SafeMode</code> the problem goes away, and it is project-specific.</p>
  
  <p>I've run Process Explorer and discovered this thread<br /><strong>(note: not the highlighted one but the thread on top)</strong><br /><br /><img src="https://i.stack.imgur.com/ORoTT.png" alt="IsAssertEtwEnabled"></p>
  
  <p>Then I found this forum related to it: <a href="https://connect.microsoft.com/VisualStudio/feedback/details/873579/high-cpu-usage-possibly-after-updating-to-update-2" rel="nofollow noreferrer">https://connect.microsoft.com/VisualStudio/feedback/details/873579/high-cpu-usage-possibly-after-updating-to-update-2</a>
  But I don't have either Power Tools or Alternating Line Color extensions installed.</p>
  
  <p>If it's not any extensions (I haven't added any), what could the issue be? The only thing I can think of is the NuGet packages.</p>
  
  <p><strong>EDIT</strong> I found this thread <a href="https://stackoverflow.com/questions/23657624/asp-net-cpu-issue-working-with-kendo-ui-treeview-after-visual-studio-2013-update">Asp.Net CPU issue working with Kendo UI treeview after Visual Studio 2013 Update 2</a> and tried the solution of disabling Browser Link to no avail.</p>
  
  <p><strong>EDIT</strong> I also disabled Source Control as described here <a href="https://stackoverflow.com/questions/22785140/vs2013-update-1-permanent-cpu-usage-even-though-in-idle-mode">VS2013 permanent CPU usage even though in idle mode</a> but apparently it is not fixed in Update 2 as the question states.</p>
  
  <p><strong>EDIT</strong> debugging and pausing the culprit thread (main thread) gives me this stack trace more often than not: <img src="https://i.stack.imgur.com/PSMyN.png" alt="stack trace"></p>