Visual Studio "Silent" Crashes...
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
Yes. I used to get that problem. Generally when building solutions with WPF components in them. It all kicked off after installing SP1. I used to get a very cryptic message in the event log. Never really found a reason, did a few uninstall/reinstall cycles and eventually it just went away. Came back once a few months later. Again after bugging me for a day or two, and not being able to find a solution it just started working fine again.
Simon
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
Yeah - I get 'em in 2008. No idea why - haven't yet figured out the circumstances. I sometimes encounter another (similar?) problem - 2008 just stops responding. I can click menus, in text, buttons, etc but nothing happens. Except for the X (close) button which actually works and closes 2008. What gets me is that I don't even use VS 2008 that much. I've been using Netbeans much more than VS lately. Netbeans rocks!
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
There was a stack overflow in earlier versions that would do that when loading a .cpp file with a > 256 char name. It was fun, I liked it. :)
-
Yes. I used to get that problem. Generally when building solutions with WPF components in them. It all kicked off after installing SP1. I used to get a very cryptic message in the event log. Never really found a reason, did a few uninstall/reinstall cycles and eventually it just went away. Came back once a few months later. Again after bugging me for a day or two, and not being able to find a solution it just started working fine again.
Simon
Simon Stevens wrote:
Generally when building solutions with WPF components in them
Recently I was doing some Silverlight dev at work and it happened a few times there. But it's also happened in VS 2005 on regular projects.
Kevin
-
There was a stack overflow in earlier versions that would do that when loading a .cpp file with a > 256 char name. It was fun, I liked it. :)
You're kidding right? How on earth could basic errors like that *still* be occurring?
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog Just Say No to Web 2 Point Oh
-
You're kidding right? How on earth could basic errors like that *still* be occurring?
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog Just Say No to Web 2 Point Oh
Haven't seen this since the last millenium, and for all I know could have been an addin - oh, and probably == not > than 256. It *was* however, good clean family fun. Really. :)
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
Silent crashes can be caused by buffer overflows or when an exception is thrown when in the destructor of an object already being unwound as part of another exception. regards,
Jonathan Wilkes Darka[Xanya.net] [My Code Project Articles]
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
Mine used to only on startup, but that was a problem with an IE cache and the Start Page feed.
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
-
...In VS 2005 and 2008. Do others get them? That is, where VS crashes with no error dialog. It just disappears. Spooky.
Kevin
Yes. I also discovered that when my project gets into a state of exiting upon recompile that opening a XML file of any kind would also cause it to immediately crash. After 5-10 restarts and cleanups it "fixes" itself. This started happening to me after upgrading to ASP.NET MVC RC1. Prior to that it never happened.
Todd Smith