Search

Visual Studio 2008 IDE Crashes Returning to Design Mode When Stopping Debugging Native C++ Code by Adzm

Closed
as Fixed Help for as Fixed

1
0
Sign in
 to vote
Type: Bug
ID: 373507
Opened: 10/7/2008 5:59:11 AM
Access Restriction: Public
0
Workaround(s)
4
User(s) can reproduce this bug
After debugging (either through Stop Debugging on the menu or through simply exiting the debuggee), the IDE may crash. Reproducible on demand by moving the output window to dock to a new pane during debugging, then stopping debugging by exiting the application or by choosing Stop Debugging. Problem appears to be an access violation. I've attached windbg to it, and have callstacks and a memory dump available.
Details (expand)
Product Language
English

Version

Visual Studio 2008 Service Pack 1
Operating System
Windows Vista
Operating System Language
English
Steps to Reproduce
Debug a native C++ MFC application. Move the Output window to dock to a different pane. Stop Debugging, IDE crashes returning to design mode.

I've been unable to reproduce with simpler applications, however several others in our organization have the same issue, same callstack, who have different machines (ie, Windows XP). We are all on a clean, brand new install of Visual Studio 2008 with SP1. No additional tools or Add-Ins are installed.
Actual Results
Access Violation. This callstack pattern is consistent with all the crashes:

0xe58b5e59
msenv!CDockManager::PruneAllDeadPanes+0x45
msenv!CDockManager::SaveUI+0xb7
msenv!CPane::TransitionToDesign+0x46
msenv!CVsShellDebugMgr::m_OnModeChange+0xe6
msenv!CVsUIShell::OnModeChange+0x21
vsdebug!CDebugger::SetShellMode+0x9b
vsdebug!CDebugger::OnModeChange+0x44
vsdebug!CDebugger::SetDebugMode+0x69
vsdebug!CDebugger::OnDebuggingStopped+0x105
vsdebug!CDebugger::HandleEvent+0x8ae

Memory dumps available.
Expected Results
Returns to design mode from debug mode with no issues.
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
File Name Submitted By Submitted On File Size  
windbg.log (restricted) Adzm 10/7/2008 -
vs9crash.zip (restricted) Adzm 10/7/2008 -
Sign in to post a comment.
Posted by Adzm on 3/18/2009 at 9:51 AM
Works perfectly. I am ecstatic!
Posted by Microsoft on 3/17/2009 at 8:55 PM
In addition to making sure this issue is addressed in VS 2010, we have been pursuing producing a patch for VS 2008 SP1 to resolve this issue. This has been released on the code gallery - please see: http://code.msdn.microsoft.com/KB960075. If you find the patch does not resolve this problem, please reactivate with details.
Regards,
Visual Studio Platform Shell Team
Posted by Andy Champ on 1/13/2009 at 3:21 AM
I've just linked to this and get a crash at the same address, also from PruneAllDeadPanes. I get it in a different and far more consistent manner; the lower parts of the call stack are different.
All I have to do is load VS2008, and undock a window. Then close it.
As I have a two-monitor system I keep the code on one screen, and undock other windows (errors, output, search result) to the second monitor. The result of this is that every time I close VS it crashes, and loses all my settings.
I can reproduce this every time, so if anyone wants a fix tested...
Posted by GregUzelac on 11/6/2008 at 11:59 AM
We run VS2008 SP1 and see this when ending a C# debug session. If the IDE Output/Errors pane is flaoting when we exit the app, or stop debugging, the IDE dies. The stack is:
0x330001ca <this varries>
msenv!CDockManager::PruneAllDeadPanes+0x45
msenv!CDockManager::SaveUI+0xb7
msenv!CPane::TransitionToDesign+0x46
msenv!CVsShellDebugMgr::m_OnModeChange+0xe6
msenv!CVsUIShell::OnModeChange+0x21
vsdebug!CDebugger::SetShellMode+0x9b
vsdebug!CDebugger::OnModeChange+0x44
vsdebug!CDebugger::SetDebugMode+0x69
vsdebug!CDebugger::OnDebuggingStopped+0x105
vsdebug!CDebugger::HandleEvent+0x8ae

Microsoft, what version is the (possible) fix slated for?
Posted by Microsoft on 10/28/2008 at 5:43 PM
Thanks again for providing this product feedback. The next release of Visual Studio will include a major rewrite of much of the code involved in the scenario you reported; we will include your user scenario in our product testing.

Thanks,
Visual Studio Platform Shell Program Management
Posted by Adzm on 10/20/2008 at 10:33 AM
Also easily reproducible if you have an application that might take a bit to close. Simply close that application, quickly switch to the IDE and drop down the Debug menu. When the application fully exits and the IDE goes back into design mode, the crash occurs, with the same call stack (for the most part).
Posted by Adzm on 10/9/2008 at 5:57 AM
Thank you very much. This problem has been incredibly irritating, to the extent that I avoid re-arranging my windows in debug mode, due to fear of a crash when I stop debugging! Any help would be greatly appreciated.
Posted by Microsoft on 10/8/2008 at 11:27 PM
Thanks for your response. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 10/7/2008 at 7:25 PM
Hello

Thanks for your feedback. Could you please upload your dump files to the following workspace? And we will re-investigate.
https://sftus.one.microsoft.com/choosetransfer.aspx?key=71175ac9-03eb-4dee-9fb2-e64f28170eae
Password:dS@RzVu1Optj



Thanks,
Kylin
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement