Just wondered if anyone else had experienced a drastic slowdown in responsiveness of Visual Studio 2010 with the latest version of Nsight Tegra? I think this may be an issue with the adb task not responding correctly, because if I manually kill adb.exe from the Task Manager then VS2010 will start to respond again.
After a little more investigation, VS2010 seems to get slower and slower every time I run the apk without debugging (Ctrl + F5), until eventually a single core of my machine is maxed out and VS becomes unresponsive.
hi NworbLegin,
I sorry that you meet this. this should not be thus. but I tried to reproduce on my box. I can’t reproduce your case. could you give more details about your case or simple sample to reproduce ?
I’ve un-installed the Tegra tools and re-installed but this problem is still here. I don’t think there is a simple sample I can put together to help you reproduce this, as it seems to be a problem in general with Visual Studio and the Tegra tools. At the moment I am forced to kill Visual Studio after 4-5 debugging sessions because it has become unresponsive.
I’m running VS2010 SP1 with Windows 8 64bit on an Quad Core i7 (pretending it has 8 cores). It’s only one of the 7 visible cores that are showing as maxed out in the resource manager.
A further update to this. Even if I don’t start any debugging sessions VS seems to become unresponsive after a period of time. Could this be a bug with the android debug logging? This problem happens if the logging window is active or not. Disconnecting the device sometimes brings VS back to life, but more often I have to kill the multiple adb instances and restart VS.
Every computer at our studio suffers from this same problem. We are running Windows 7 64-bit.
Whenever we press ctrl-F5, Visual Studio becomes completely unresponsive, uses 100% of one core’s cpu time (in our case that’s 25% since we have quad cores), and we either have to kill the Visual Studio process or wait for it to recover. It often will not recover at all until we exit our application on the device, or disconnect the device from our PC. After that time, it can take 1-2 minutes for Visual Studio to start responding again, although I have at times left it for 15+ minutes and came back to it still stalled.
While it’s using the CPU this way, according to task manager, it’s allocating ~250K of RAM per second and the number of threads is flipping up and down seemingly at random.
It also appears to be worse when we have a large number of Android log statements, such as an error which occurs every frame.
After updating to the latest release I still have a very long delay in VS after I stop debugging my Android App. It seems that the application does not quit and visual studio takes at least a minute to become responsive again. Is there somewhere I can change a timeout value to speed this up?
This is a known issue that will be fixed in the future.
For now you could try setting Tools → Options → Android → Debug → Timeout to a lower value (1 second, for example). The delay scales with the number of breakpoints, so keeping it low will help the matter as well.
