VS 2010 becomes unresponsive randomly. A look into process monitor shows it waits in a loop on RegQueryValue operation on HKLM\SOFTWARE\Microsoft\Cryptography\Defaults\Provider Types\Type 001\Name key. Why does Visual Studio need to do this? Is there a way to get around this?
Have tried resetting devenv and stopping Windows Cryptography Services.
Related
I've always used System.Diagnostics.Debugger.Launch() as a quick way to debug web services. I get a dialog asking me to choose a debugger, I pick "New instance of Visual Studio" and it fires up VS and lets me step through the code.
That has suddenly stopped working. Now I get the dialog, and choose Visual Studio, and the VS splash screen appears, and then it just hangs. The dialog window says "Not Responding" and I have to force it to close. Even then, a VS instance is left hanging around in Task Manager and I have to kill it manually.
I've tried repairing Visual Studio, and uninstalling and reinstalling Visual Studio, and nothing fixes it.
In desperation, I completely flattened my PC and reinstalled everything from scratch. It lasted about a day and then JIT debugging started hanging again. I was on Windows 10 and Visual Studio 17.4.1 before, and I'm on Windows 11 and Visual Studio 17.4.2 now.
To make sure that it's not a problem with some particular code, I created a one-line console app System.Diagnostics.Debugger.Launch(); and that crashes just the same.
Has anybody experienced anything similar, or have any idea what could be going wrong?
I don't know why that fails, but I suggest to attach to a running instance of Visual Studio instead. Start Visual Studio first, and then when the "launch debugger" window appears, select the running VS instance. Preferably, you should even open the correct solution/project first. If you attach to that instance, all your source code and the project structure is available for debugging.
Another alternative: Instead of using Debugger.Launch(), use a code snipped such as
while (!Debugger.IsAttached)
{
Thread.Sleep(100);
}
at the beginning of your program and attach the debugger from within Visual Studio (using the menu option Debug->Attach to process)
I had the same exact problem and after updated to VS version 17.4.4 the issue disappeared. All good now.
I have noticed a frustrating problem during which a standard Winform control will not enter a drag-drop operation during a debug session as it should after calling the control's DoDragDrop method. The source control (from which the drag-drop operation is initiated) acts as if it doesn't support drag-and-drop.
In my case, it turns out that I was running a debug session in a second instance of Visual Studio 2017. When I stopped running that second debug-session instance of Visual Studio (I was able to keep Visual Studio open, I just had to stop my debug session), the drag operation in the first debug-session instance of Visual Studio began working as expected.
Clearly, drag-and-drop should work in two debug sessions open at the same time in two different Visual Studio instances--and sometimes it does on my system. But occasionally something happens (I'm not yet sure what) to "corrupt" the VS IDE or the .NET subsystem that causes a Winform drag operation from no longer functioning.
This behavior occurs even after rebooting and happens in the latest VS Enterprise 2017 IDE (Ver 15.5.6) with .NET 4.7.02556.
I realize that this problem and its solution is rather nebulous but I felt it was enough to be useful here (and I invested a lot of time figuring out what was going on!).
For the past couple of days, Visual Studio 2012 and 2013 have been hanging during debug mode. Most of the time, i dont get this issue until further into my project. When i press the Start Button, everything continues as normal, but then hangs with this message at the bottom of visual Studio statusBar.
Inside Task Manager, when i try to force taskkill, or end process/process tree, this continues to stay present in my running processes.
Even after a reinstall, nothing seems to help it. I did see somewhere on the Microsoft Developer forums where a person was told it was something to do with the windows sybmol server?. What do i need to do to fix this issue i am having?
After this occurs once, i am forced to reboot my computer. Even if i open Visual Studio after this happens, it still has the same issue.
I'm working with some clunky old (massive) Microsoft Access databases and, as a result, Visual Studio 2010 is regularly crashing on me.
When I try to use the Data Source Configuration Wizard it basically freezes and tells me that 'Visual Studio is Busy' and then doesn't come back. Not only this, but it locks the Access database.
I've tried Ctrl + Break and Ctrl + End with no joy, I always have to kill it with task manager, and I lose anything I haven't Saved/Commited since my last build!
Does anybody know of a more eloquent way of telling Visual Studio that you've changed your mind?
Thanks
As far as I know, when it says it's busy, you can't interrupt it. It might be a problem with your installation. Did you try it on a freshly installed Windows + Visual Studio?
Another thing you can try is download Visual Studio 11 Developer Preview and see if they have fixed the stability issue.
Sometimes I experience Visual Studio 2010 being very sluggish. I have some plugins, like ReSharper for example, that I think could be the culprit.
It would be nice if I could see the processes under visual studio to see what is using up all the CPU. Basically what I am looking for is a Task Manager just like the one in Google Chrome but for Visual Studio. I searched the internet and came up with nothing.
Unlike Chrome, Visual Studio does not use multiple processes. (Except when debugging applications)
Using Process Explorer you can double click on your devenv.exe process, then under the Threads tab you can inspect, suspend or terminate (I wouldn't recommend the latter) threads belonging to addons, for example, VAssistX threads generally have a start address somewhere in the va_x.dll region.