I just added a third monitor to my system (NEC E222W) which my NVidia GeForce 9500 GT card is able to rotate such that I get 1050x1680 resolution. However, when using this mode Visual Studio 2010 SP1 (10.0.40219.1 SP1Rel) consistently locks up (grabbing 50% of the CPU) until I kill it whenever I interact with TFS. I can work in VS 2010 until I try to do anything with TFS.
I can open up Visual Studio without issues on my other two monitors and check stuff out, etc., but the minute I move the application to my 1050x1680 monitor and start the TFS dialog, the application hangs.
Anyone have this issue? I'm pretty current on the NVidia driver (191.07) and Windows XP SP 3 is current with Microsoft Update. I'm running under a non-administrator account.
Internet has not been helpful. The only thing I found was this:
http://social.msdn.microsoft.com/Forums/en/vseditor/thread/ce9134aa-b444-49e8-99f2-01b67404156a
This: Visual Studio 2010 Freezes when using TFS is unrelated.
I am able to fire up VS 2010 on the 1050x1680 monitor, work, then shift the existing instance over to another monitor to interface with TFS (check in/out) and then shift the application back to the 1050x1680 monitor successfully. I strongly suspect something is broken with the TFS checkout dialog window.
Related
Dealing with an extremely annoying issue and unable to find a resolution so far around the web.
Issue description:
Using Visual Studio 2019 Community Edition, and after a bit of debugging, stepping through code and inspecting objects in Quick Watch I notice that mouse movement begins to lag. Mouse pointer is still movable but is jumpy, like bad wireless mouse connection. Extremely annoying as I first though wireless mouse was at fault. But the issue goes away immediately after Visual Studio is closed. This is also very reproducible, although does not appear to happen right away, seems to happen after a few debug sessions.
Things I've tried:
Uninstalled all Visual Studio extensions
Reset all Visual Studio settings and performed "Repair" from VS Installer
Disabled Windows Defender, no other anti virus / spyware software is running
Updated Windows 10 to latest update
Updated Visual Studio to latest version as of now
If anyone has any suggestions on how to fix this, please share.
If you are experiencing the same issue, please add details about your environment in comments (Visual Studio edition & update version, .NET version of the project, Windows update version).
enter image description here
This is mainly caused by hardware acceleration feature which is caused by Grafics Card bugs.
The Visual Studio team has continued to notice a small but important series of performance and reliability issues that are caused by bugs in the installed graphics drivers. By default, Visual Studio automatically adjusts the visual experience in order to maximize performance and responsiveness across client configurations. Visual Studio also uses hardware graphics acceleration when it is available on the client. For most customers, these Visual Studio default settings provide the best user experience. However, some users have reported that manual adjustments to these settings can result in improved experience. This article describes how to make these adjustments in Visual Studio.
Solution :
Disable "Use hardware grafics acceleration if available" in visual studio settings (Tooles -> Environment -> General)
enter image description here
I have some web projects that run fine in the debugger in VS 2012. But when I try to run the same projects in VS 2013 i run into some problems.
First the whole Devenv.exe crashed when pressing F5.
I found an article about this problem here
It suggests set ISS Express in Visual Studio to 64 bit.
That solved the problem of the whole IDE crashing.
However, with that configuration Visual Studio tries to start "Remote Debugging". Probably because Visual Studio itself is 32 bit, so it must use some "remote" techniques to debug something 64 bit. At least that's my guess on what is happening.
Remote debugging is not succeeding either. I get "Remote Debugger has stopped Working" sometimes. Sometime at the beginning of the degugging session, and sometime at the end of the session. I found an article about this problem too. It suggest to set the web project to x86 to avoid remote debugging. But that will not work in this case. It has to run 64 bit to work with IIS in 64 bit.
Error message is
Remote Debugger has stopped Working
Then
The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted.
Anyone else seen this?
Is this a common problem in Visual Studio 2013?
EDIT: more details about the environment
I have a solution containing several projects, including two web projects.
The issue happens when I try to run any of the web projects in debugger (by pressing F5).
They are normal web projects, and I am not running anything remote.
Visual Studio itself came up with the idea of using "Remote Debugger" when I checked the "Use the 64 bit version of IIS Express for web sites and projects".
The solution was first created on a Windows 7 machine running Visual Studio 2012 and it worked well there.
When I tried to open the same solution on a new machine running Windows 8.1 and Visual Studio 2013 the problem started.
A colleague is also running the same solution on his Windows 8.1. We share the solution using a git repository.
He has both VS 2102 and VS 2013 installed. He experiences the same problems in VS 2013, so he has started to use VS 2012 for this solution.
It runs fine in VS 2012. It is the same solution and same machine as it fails in VS 2013.
I have Visual Studio 20010 Ultimate on Windows 2008 R2 machine. Last week I applied SP1 and after few days I am experiencing UI freeze for some time around 40 to 60 seconds when I save code changes to files.
I have turned off the background compilation, turned off the antivirus still this problem is not going away.
On my 2008 R2 machine I right clicked on the shorcut for VS2010 and selected properties option. In compatability tab I selected to run VS in compatability mode for Windows server 2008 SP1. There is a checkbox and dropdown for this.
For VS 2010 SP1 it is mentioned that it sets software rendering by default. I thought this might be the reason for UI freeze in some case hence I changed the compatibility setting and it seems to be working fine since then!
[With Visual Studio 2012] Try pressing ATL+TAB twice (or switch to another application then switch back to Visual Studio).
That seems to solve the problem.
Mostly it happens if we open a team project from tfs 2008 or tfs 2010, but crashes can happen any time.
When VS is closing down, it crashes nearly every time.
Tried trial RTM and our MSDN download - same story. Tried on three different PCs - same issue. Tried on 32 and 64-bit Windows 7 and Windows Server 2008 R2 - crashes.
Is it just our luck or does it happen to you to?
Here are some tips that will hopefully help you identify the problem:
http://blogs.msdn.com/kirillosenkov/archive/2010/02/08/how-to-investigate-and-report-visual-studio-issues.aspx
Ideally, get a call stack of the devenv.exe main thread with symbols loaded, and post it here (or even better), attach to the Connect bug. From the stack we'll likely be able to tell what kind of problem it is.
I logged it as an issue on Microsoft Connect.
There is a new release of the TFS Power Tools and Visual Studio 2010 Productivity Power Tools which seem to reduce the instances of VS crashing (although it still seems to crash from time to time). It might be worth checking out if you use either add-in.
Apparently, the crash was caused by using a DNS name in Connect to Team Foundation Server.
I replaced that with the IP address of the TFS server and the crashes went away.
We have two Windows Server 2003 DNS servers, and it looks like Visual Studio 2010 does not communicate with them correctly. Visual Studio 2008 connects to the TFS without any issues.
Apparently, there a bug:
"Large Visual Basic project crashes when closed"
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=29797
I'm working on Visual Studio 2008, Smart Client + infragistics controls are installed and we have more than 50 User Controls. When opening the Visual Studio "Tool Box", Visual Studio is completely freezing. I couldn't work after that. I have to kill the process and open again. At this point CPU usage is around 50, CPU usage is 1 or 2 when i work on code. How to get rid out of this issue. This is really time consuming process.
try:
Visual Studio 2008 takes a long time to open the toolbox for a solution that contains many custom controls
The KB article recommends downloading and installing a hotfix.