问题描述
如果我构建,IDE将进入100%CPU 2分钟
如果我发布IDE进入100%CPU 2分钟
如果我背靠背构建然后发布IDE永远不会停止做它正在做的事情,通常会吃掉2.6G的内存和崩溃。一旦IDE耗尽了尽可能多的CPU,你最好只是杀死现有的VS2015并重新开始。新的
实例将使用高CPU不到30秒并停止。
它没有做任何可以帮助你调试的事情,否则新实例必须完成它开始之前。
我目前使用VS2015的最佳做法是编译,发布,存在并重新启动VS2015然后调试。
我可能会得到2个调试会话没有重新启动但通常不会持续那么久。
if I build, the IDE goes into a 100% CPU for 2+ minutes
if I publish the IDE goes into a 100% CPU for 2+ minutes
If I back-to-back build then publish the IDE never stops doing whatever it's doing and usually eats up 2.6G of memory and crashes. Once the IDE is eating up as much CPU as it can you are better off just killing or existing VS2015 and starting over. The new instance will use high CPU for less than 30 seconds and stop.
It's not doing anything that helps you debug or else the new instance would have to finish that it started before.
My current best practice with VS2015 is to compile, publish, exist and re-start VS2015 then debug.
I might get 2 debug sessions without restarting but it usually doesn't last that long.
这篇关于VS2015几乎一文不值的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!