Visual Studio 2010编辑器缓慢分解，然后使用100％CPU冻结 [英] Visual Studio 2010 Editor breaking down slowly then freezing with 100% CPU

问题描述

我今天开始使用VS 2010编辑器出现了一个新问题。

当我点击一个标签时，我会像往常一样在一个项目上工作编辑一些代码，该选项卡不起作用。代码不存在或部分存在并且点击周围工作（可以突出显示空白区域）然后根本不工作。其他
选项卡仍可正常运行，但是，在稍微点击一下之后，它们也会开始中断，最后整个VS UI变得无法响应。什么都不起作用（菜单，最小化等等）和devenv进程在一个CPU上吃掉100％。只有停止的方法是杀死
进程并重新启动VS.这已经发生了三次。

我只试过一个C＃WPF项目的解决方案。它需要几个小时才能发生，因此在我需要实际处理它们之前，我不能轻易地使用其他解决方案进行测试。作为XAML +设计器的选项卡也会分解（无法交互）
但所有内容（XAML和设计器）仍然可见。

任何想法？

谢谢，

安德鲁

解决方案

嗨安德鲁 - 下次发生这种情况时，可以你
收集挂起转储 当进程使用100％CPU时（该链接引用Visual Web Developer，但步骤应该适用于任何版本的Visual Studio 2008或2010）和
提交连接错误 功能？;这将为我们提供一个良好的调查起点，如果我们需要更多关于逐渐下降到无反应的信息，我们可能会要求您提供更多详细信息。 如果您愿意，可以随时发布错误的Connect错误ID，并确保尽快找到合适的人。

感谢您试用Visual Studio 2010并发帖您的意见！

$
Brittany Behrens |项目经理| Visual Studio平台 - 编辑器  |
Visual Studio Blog |在Twitter上
Twitter上的@ VSEditor < /跨度>

I have a new problem which started today with the VS 2010 editor.

I'll be working as usual on a project when suddenly when I click on a tab to edit some code the tab is non-functional. Either the code is not there or is partially there and clicking around works briefly (can highlight empty space) and then not at all. Other tabs remain functional, however, after a bit more clicking around, they also start breaking and finally the entire VS UI becomes unresponsive. Nothing works (menus, minimizing, etc..) and the devenv process eats up 100% on one CPU. Only way to stop is killing the process and restarting VS. This has happened three times today.

I've only tried with one solution which is a C# WPF project. It takes several hours to happen so it's not something I can easily test with other solutions until I need to actually work on them. The tabs that are XAML+designer also breakdown (can't interact) but all the content (XAML and designer) remain visible.

Any ideas?

Thanks,
Andrew

解决方案

Hi Andrew - Next time this happens, could you collect a hang dump when the process is using 100% CPU (the link references Visual Web Developer, but the steps should work for any edition of Visual Studio 2008 or 2010) and file a Connect bug?  That will give us a good starting point for investigation, and if we need more information about the gradual descent into unresponsiveness we might ask for more details.  If you'd like, feel free to post the Connect bug ID for the bug and I'll make sure it gets to the right people ASAP.

Thanks for trying Visual Studio 2010 and posting your feedback!

Brittany Behrens | Program Manager | Visual Studio Platform - Editor | The Visual Studio Blog | @VSEditor on Twitter

这篇关于Visual Studio 2010编辑器缓慢分解，然后使用100％CPU冻结的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！