I have a VB.Net windows forms application that has been around for a very long time. I am working the project in Visual Studio 2010 Premium, on my Windows 7 x64 workstation. Everything has been going along fine till a couple days ago. No every time I build this project Visual Studio 2010 crashes.
The only thing i have to go on is this from another Visual Studio 2010 instance that attached the debugger to the dieing process.
...
The thread 'Win32 Thread' (0x177c) has exited with code -2147023895 (0x800703e9).
The thread 'Win32 Thread' (0xc44) has exited with code -2147023895 (0x800703e9).
The program '[4224] devenv.exe: Native' has exited with code -2147023895 (0x800703e9).
No one else on my team has this issue, and I don't have problems with any other projects.
This is .Net 4.0.
Any thoughts or suggestions are much appreciated,
Beezler
It might be wise to start VS with the /safemode parameter.
I also had this problem and I solved it by uninstalling the Achievements extension.
Do you have any modifications whatsoever to the solution/projects/code that are different from the team members not experiencing the crash? Have you tried getting a fresh-cut of the source to a different directory and trying to build that?
Another thing to look at would be to disable any add-ins/extensions you might have installed.
I had the same problem but with C++ projects. They ran fine for a while, then all of a sudden just started crashing on every build. This fixed it for me:
To fix: click start, type "cmd" into the search box, right click "cmd.exe" in the search results, select "run as admin", then run this command: regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
If that doesn't work, the plugin AnkHSVN is known to cause the same problem. http://blogs.msdn.com/b/visualstudio/archive/2010/05/11/if-you-are-seeing-intermittent-crashes-with-vs-2010.aspx
This is weird and i've also faced a similar issue like that. First i add a watch to a class. and when i try to drill to details of class collection, process terminates and debugging stops.
I've figured out that, it is giving stackoverflow error code. Base of the exception was just because of infinite loop.
So i re-checked all collections twice to find the property that causes a loop. like int a {get {return MethodThatAlsoReturnsA();}
hope it helps s.o.
User contributions licensed under CC BY-SA 3.0