If you are seeing intermittent crashes with VS 2010

If you are seeing intermittent crashes with VS 2010

  • Comments 60

Some customers have been reporting intermittent crashes while using Visual Studio 2010, particularly during file save and build. We haven’t tracked this down completely yet, but many of the crashes seem to be related to an out-of-date version of the AnkhSVN extension. The newest release (2.1.8420note correction – 8400 did not fix the problem and is no longer offered on the AnkhSVN page) contains a fix that we believe solves the AnkhSVN problem. You can download the latest release of AnkhSVN here.

Gary Horen, Program Manager, Visual Studio Platform

Leave a Comment
  • Please add 8 and 7 and type the answer here:
  • Post
  • Note I do not have any addins etc. loaded in VS.

  • @Neal: Please open separate Connect bugs. From your description it sounds like you have 2 issues (VS crashing, and VS hanging during builds), and if you're not using AnkhSVN this thread does not apply to you.

    Please attach to the Connect issues as much information as you can gather (minidumps or Watson report numbers during crashes or minidumps when VS hangs, etc) - if not someone will reply to the Connect bugs and tell you how to capture these.

  • VS 2010 keeps crashing for me.

    Windows 7 Pro , only addin is Active Reports 6

    on a super clean Panasonic TuffBook laptop.

  • vs 2010 so good

  • This worked for me: ankhsvn.net/.../2.1

  • VS 2010 is incredibly buggy in the code writing department. Especially when writing javascript inside an aspx page's script tags. At this point I now have an "intuitive" sense of when the mere act of adding curly braces and hitting enter will cause Visual Studio to "stop responding", "crash and look for solutions", etc.

    This is 5-25x a day and I constantly shutdown & restart. Further the mouse is often non-responsive and sometimes keyboard commands like left arrow, right arrow, ctrl+end stop as well.

    Further quite often (50x a day) it freezes and I have to go get coffee or smoke a butt waiting for it to stop seizing. If ya got 'em smoke 'em.

    My big beef with Microsoft is the schizophrenic nature of marketing versus reality. Endless spin-doctoring is insulting to the intelligence and one never truly believes MSFT cares about coders; specifically web developers.

    Even IE9 is still slow compared to chrome & FF and despite massive HTML5 propaganda does not even support HTML5 uploads.

    I am an MCSD.NET and I have given up my MSFT consulting practice to launch a startup and I have abandoned Azure in favor of Amazon S3, am leaning more & more towards JQUERY, and if it weren't for the Telerik control suite all would be lost.

    MSFT is a great company, no doubt about it, but they lack integrated leaders who can snap all the puzzle pieces together seamlessly and they miss the fact, true partnering with developers means integrating IE9, VS 2010, and dealing with the crashes, roadmaps, etc. in ways that do not make people curse them whilst the PCs are a crashing.

    And believe me, I develop on a POWER EDGE server with 12 gigs of RAM and massive processing power because otherwise I would get NO work done. But the truth is I gave up sleep to get my ASP.NET start up going and 1/5th the time is wasted on crashes. Multiply that across the industry and we could be in the year 2020 by now technologically speaking.

    I would suggest MSFT leaders check out www.neo-tech.com and Mark Hamilton's Cosmic Business Control for a primer on integrated thinking vis a vis solving the aforementioned.

    Peace out!

    Cary

  • Started Crashing since SP1 (VS 2010)

    .

    Only 'Crashes' completely occasionally. BIG problem is the coooonnnnsstannt need to debug the .designer files. my forms are always loosing stuff. mainly databound dgv's. So spend another hour removing all the useless stuff that's left behind, then another hour adding my dgv and reformatting & naming columns. THIS IS PAAAAIINNNNFULLLLLL.

  • VS2010 SP1 crashes on me constantly.  Typically every 4 or 5 builds it freezes up with the white screen of death and doesn't recover.  It's not fully frozen, behind the white screen I can see the build icon moving.  And sometimes it'll let me do tons of build without a problem, then sometimes its every build.

    I have never installed AnkhSVN.  Initially I did think it was some third party add-in, so I reinstalled with Windows 7 Ultimate x64 and just used plain old Visual Studio for a while with no third party add ins, it still exhibits this behavior, but maybe less often...

    Not sure if it helps but using multiple monitors with VS2010 (geforce gtx 280)

    Please help, this is tedious...

    Thanks!

    Matthew

  • @Matthew

    Have you tried installing the Perf Watson tool (visualstudiogallery.msdn.microsoft.com/fa85b17d-3df2-49b1-bee6-71527ffef441) so that we can get information on these hangs for investigation?

    When you say it is 'crashing' but then you say it is going to the 'white screen', those are two different things.  The white screen happens when windows determines a program is unresponsive (i.e. it is busy doing some kind of work and not responding to messages).  Generally 'crashing' means it is actually terminating and a WER (Windows Error Reporting) dialog is coming up.  If it is the former then Perf Watson can grab information about these occurances that will help us troubleshoot it.  If it is the latter then you grabbing a dump of the process could be helpful for us understanding what is going on exactly.

    Ryan

  • From the Problem Details text:

    Description:

     A problem caused this program to stop interacting with Windows.

    Problem signature:

     Problem Event Name: AppHangB1

     Application Name: devenv.exe

     Application Version: 10.0.40219.1

     Application Timestamp: 4d5f2a73

     Hang Signature: 3e47

     Hang Type: 0

     OS Version: 6.1.7601.2.1.0.256.1

     Locale ID: 1033

     Additional Hang Signature 1: 3e47011304665480bdc8f0af432eb84d

     Additional Hang Signature 2: bccf

     Additional Hang Signature 3: bccff7c08904020b796ab2062636623b

     Additional Hang Signature 4: 3e47

     Additional Hang Signature 5: 3e47011304665480bdc8f0af432eb84d

     Additional Hang Signature 6: bccf

     Additional Hang Signature 7: bccff7c08904020b796ab2062636623b

  • @Ryan

    Sorry for the confusion, VS never crashes on its own, just hangs to white screen.  I’ve tried leaving it alone (for several hours) to see if it would recover, it never does.

    I did install PerfWatson, it appears after I close a hung instance of VS and restart it, I’m now sending in the reports.

    Is there anything else I can do now aside from wait for a patch that may never come?

    Appreciate the help,

    Matthew

  • @Matthew

    No problem, just wanted to make sure I understood which of the two scenarios you were seeing, or see if you were seeing both.

    As for the PerfWatson stuff, it is good that it is sending data, that means it is catching the hangs and giving us call stacks when they occur, which would allow us to see WHAT is going on exactly.  

    As for near term solutions / work-arounds, I am checking internally to see if there is any way for us to correlate data sent to us with you specifically (the process is set up to not include Personally Identifiable Information (PII)). If we can I could look for your hang data specifically and see if I can see what is causing it and if we can figure out a work around.

    Ryan

  • Hi Ryan,

    I started to experience the same issue recently...

    Message and progress bar popping up advising me

    that Visual 2010 (Utimate) needs to be shut down and restarted...

    Feeling a bit like motor stalling when light just turns green in the middle of traffic...

    Aaaaaaaaaargh!

    I'm basically working mainly on Silverlight 4 + WPF applications right now

    though I never encountered this issue up to recently.

    Everything has always been running smoothly... I'd like to mention

    that the Windows Phone 7 version saga has forced me to make a lot of updates

    in a short period of time, though all in all it didn't seem to have

    any negative impact 'cause like I said I never encountered any similar issue previously.

    Now I'm not saying that this is THE cause, though I have some reason to believe

    that it may be somehow related to a Telerik JustCode AddIn I installed on Visual Studio 2010

    recently... I'll guess I'll have to create a dump and have a closer look to see what happens...

    Keep you in touch...  Thank's

  • @Mawashikid

    >that Visual 2010 (Utimate) needs to be shut down and restarted...

    Yes, that sounds like a crash not a hang, attaching a debugger (even VS) to the crashing process and getting a full dump would be useful, I can set up an upload location if you get one (it will be a few hundred megs).  

    It could very well be related to third party add-ins, VS generally doesn't do a 'catch all' approach as it could leave the entire app in an unknown state and continuing to run could cause all kinds of fun things like data corruption or bizaare bugs that are impossible to reproduce (since they are due to corruption).  

    There are some locations where the moral equivalent of a 'catch all' is in place, specifically on COM boundaries, but since VS allows for people to directly contribute UI there are many places where there is nothing between VS and crashing but the message pump near the bottom of the application stack, and all we could do to prevent it there would be __try / __catch and ignore all exceptions, which I personally think would be a very bad idea :)

    Ryan

  • @Mawashikid

    >that Visual 2010 (Utimate) needs to be shut down and restarted...

    Yes, that sounds like a crash not a hang, attaching a debugger (even VS) to the crashing process and getting a full dump would be useful, I can set up an upload location if you get one (it will be a few hundred megs).  

    It could very well be related to third party add-ins, VS generally doesn't do a 'catch all' approach as it could leave the entire app in an unknown state and continuing to run could cause all kinds of fun things like data corruption or bizaare bugs that are impossible to reproduce (since they are due to corruption).  

    There are some locations where the moral equivalent of a 'catch all' is in place, specifically on COM boundaries, but since VS allows for people to directly contribute UI there are many places where there is nothing between VS and crashing but the message pump near the bottom of the application stack, and all we could do to prevent it there would be __try / __catch and ignore all exceptions, which I personally think would be a very bad idea :)

    Ryan

Page 3 of 4 (60 items) 1234