VS2013永久 CPU 使用率，即使在空闲模式下

我最近更新了 VS2013到更新1，从那时起 VS 将 CPU 使用率永久性提高到25% (在一个4核的英特尔 i5 CPU 上) ，即使它应该是空闲的。我认为它有一些未完成的后台进程，所以我让它运行了一段时间，但它继续使用 CPU 时，它应该是空闲的。

更新后你是否也有类似的行为？

编辑1 : 对于 vs，我使用的是 git 和 python 工具，因此在更新1之后可能会有一些冲突。

编辑2 : VS2013中的 git 集成是错误的。我在 devenv.exe上运行了一个分析器，尽管 git2-msvstfs.dll应该是空闲的，但它占用了大部分 CPU 的使用。如果你也有同样的问题，请投票支持这个 http://connect.microsoft.com/visualstudio/feedback/details/844616/vs2013-update-1-cpu-usage-not-normal

enter image description here

编辑3 : 更新2最近已经发布，这个 bug 在 VS2013更新2中已经修复。

编辑4 : 由于多种原因(不仅仅是 git dll 模块) ，发布了更新3和4，CPU 使用量急剧增加。在下面的答案中禁用 Browser Link似乎可以解决这个问题。

26505 次浏览
小开
最佳答案

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.

小开

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

小开

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 %.

小开

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)

小开

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

小开

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


提交答案