Ask a questionAsk a question
 

Proposed AnswerVS crashes after double click on an error in the errorlist

  • Friday, October 23, 2009 4:05 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am using IVsOutputWindowPane.OutputTaskItemString to add an error message to the VS Error List. Double click on the message added through this call should show the line of the source code identified by the appropriate parameters of the method.

    It does exactly as it should, but at least on one computer it sometimes crashes the VS. There is no messages no restart - no nothing, the VS just disappears. Even if I run the VS under debugger - another instance of VS, in this other instance there is no exception or any other indication of what causes the crash.
    I cannot replicate it on other computers, but on this one it is pretty consistent - every time you click a message in the errorlist it is fifty fifty chance it will fall flat on its face.

    What else can I do to troubleshoot what's wrong?

All Replies

  • Sunday, October 25, 2009 2:34 PMRusty DeschenesModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello,

    When you run it under the debugger, make sure that you set the debugger to debug both Managed (v4.0) and Native code. Also under Tools-->Options...-->Debugger-->General, make sure that you uncheck Just My Code. These settings should help ensure that you do get to see the exception under the debugger.

    Rusty

  • Monday, November 02, 2009 7:41 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Nope, does not help. I did all what you suggested to no avail, it keeps disappearing.

  • Monday, November 02, 2009 7:49 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Some progress of a sort. If I launch it without the debugger attached, and try to replicate the issue, the dialog "Visual Studio has encountered a problem and needs to close...." shows up. From this dialog I can attach debugger and send an error report. I did both. The debugger shows access violation at some ungodly address, and the stack is a complete mess.

    By the way before the dialog to choose a debugger the "Visual Studio has encountered a problem" dialog is show twice, it seems like an exception in the exception handler.

  • Thursday, November 05, 2009 4:29 AMWeston Hutchins - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    If you can repro the crash consistently, can you capture a dump file and create a Connect Bug with the appropriate repro steps?  Ideally, you can attach your project to see if we can try to repro it as well.

    You can use the instructions here for obtaining a dump file: http://blogs.msdn.com/mikhailarkhipov/archive/2006/07/25/678308.aspx

    Thanks,
    Weston Hutchins
    Program Manager - VS Platform


    Remember to mark the best replies as answers!
  • Thursday, November 05, 2009 1:27 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I can and I will, maybe today
  • Monday, November 09, 2009 9:36 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Done and done. The dump 455MB is being uploaded. The issue ID 509371
  • Thursday, November 12, 2009 5:56 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Why did you mark this as an answer? This is not an answer - not yet. I still have the same problem and I still do not know what causes it or what to do about it, it is helpful, so I voted it up, but it is not an answer
  • Monday, November 23, 2009 6:52 PMWeston Hutchins - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Michael,

    We've received the crash dump and are currently taking a look. 

    Thanks,
    Wes
    Remember to mark the best replies as answers!
  • Tuesday, November 24, 2009 8:14 PMMichael Feingold Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Cool! If you can give me an idea on what are the chances of this happening on somebody else's computer that would be really helpful