Visual Studio and .NET Framework Home
Add-in causing stack overflow causes "Microsoft Visual Studio has encountered a problem and needs to close"
Carlos J. Quintero
as Won't Fix
2/12/2009 11:50:23 PM
User(s) can reproduce this bug
When an add-in causes a stack overflow, Visual Studio crashes with the message "Microsoft Visual Studio has encountered a problem and needs to close" rather than catching and showing the exception. This problem happens in VS 2005 and 2008 but didn't happen in VS.NET 2003.
I am not sure if this happens in VS 2010 CTP since I can't test it anymore.
Visual Studio 2008 SP1
Windows XP Professional
Operating System Language
Steps to Reproduce
Create and load add-in with this code that calls f1() and f2() forever.
public class Connect : IDTExtensibility2
public void OnConnection(object application, ext_ConnectMode connectMode, object addInInst, ref Array custom)
public void OnDisconnection(ext_DisconnectMode disconnectMode, ref Array custom)
public void OnAddInsUpdate(ref Array custom)
public void OnStartupComplete(ref Array custom)
public void OnBeginShutdown(ref Array custom)
Message "Microsoft Visual Studio has encountered a problem and needs to close"
A message with a StackOverflowException that gives the developer a clue that the problem is a recursion, and doesn't crash Visual Studio.
Visual Studio .NET 2003 did so, but somehow VS 2005 (and 2008) behaves much worse in this scenario.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 2/17/2009 at 11:39 PM
Thank you for reporting this.
We have evaluated this bug and unfortunately, it falls below the list of bugs we will be able to fix for the next VS version.
on 2/16/2009 at 12:42 AM
Thanks for your feedback. 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.
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2014 Microsoft