我在使用Visual C＃EX preSS 2010年。通常情况下它工作正常，但经常（并不总是），当我离开它打开了几天程序本身变得波涛汹涌。它需要半秒钟的鼠标点击或键盘进行注册。即使移动鼠标在屏幕上的不连贯。我试图在过去的测试，如果这是我的工作，通过运行它，并与它玩了几个小时的项目，然后离开它运行了几天，但它似乎没有任何问题。只有VCSEx press.exe似乎有问题。

I am using Visual c# express 2010. Normally it works fine, but often (not always) when I leave it open for a few days the program itself becomes choppy. It takes half a second for a mouse click or keystroke to register. Even moving the mouse on the screen is choppy. I have attempted in the past to test if it was the project I am working on, by running it and playing with it for a few hours, then leave it running for a few days, but it doesn't seem to have any problems. only VCSExpress.exe seems to have the problem.

今天我选择了发布此问题的原因是，当我开始工作，它是波涛汹涌，我将它关闭并重新启动，工作好了一个小时，然后开始变得波涛汹涌（仅一个小时后），同样的问题一如既往，将其关闭并重新启动，现在它工作正常。

The reason I chose to post this question today is that when I started working, it was choppy, I shut it down and restarted, worked good for an hour, then starting getting choppy (after only an hour), same problem as always, shut it down and restarted, and now it working fine.

任何人有任何的想法。

我在Windows编程。 C＃的WinForms。和SQL

I am programming in Windows. C# Winforms. and sql

推荐答案

Visual Studio是一个非常善变的动物，这些类型的性能问题并不少见的。由于近我可以告诉这是由资源死锁内引起了一些不同的要求骑师的权利，特定资源的其他程序中造成的，无论是鼠标，文件，图形卡，或其他任何东西，感觉它可能需要。我有过这样的表面上从字面上几十个不同的计算机具有完全不同的硬件问题。他们中的一些有除了VS2010安装任何其他的主要应用领域。

Visual studio is a very capricious creature and these sorts of performance problems are not uncommon at all. As nearly as I can tell this is caused by resource deadlocks within among other programs that cause a few different requests to jockey for rights to a specific resource, be it the mouse, a file, the graphics card, or anything else it feels it might need. I have had problems like this surface on literally dozens of different computers with wildly different hardware. A few of them have no other major applications installed besides VS2010.

我已经能够找到有助于控制问题的唯一一件事就是使用一个程序一样的过程套索，这将允许您设置核心亲和力负载视觉工作室，从使用第1或2个内核的机器上限制VS。这不能完全解决问题，但在我的经验，使得它不太常见，也降低了严重性，当它发生（它，至少，不是冻结基本的文件浏览和任务按Ctrl-Alt-Del组合杀的过程中着急）。

The only thing I have been able to find that helps control the problem is to use a program like Process Lasso, which will allow you set core affinity for visual studio on load, to restrict VS from using the first 1 or 2 cores on the machine. This will not fix the problem completely, but in my experience it makes it less common and also reduces the severity when it happens (it will, at least, not freeze basic file navigation and mandate Ctrl-Alt-Del to kill the process in a hurry).