StackOverflowException will crash vstest.executionengine.x86.exe - by Andrew Ritz

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 743160 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 5/22/2012 10:06:16 AM
Access Restriction Public


When running unit tests in VS11, any test that has a stack overflow (and throws StackOverflowException) will crash the execution engine nine times out of ten.  Sometimes UnitTestExplorer will just show that the test in question wasn't run, or that there is some unspecified error.
Sign in to post a comment.
Posted by Mohideen Sandhu MuzafarGani on 12/13/2012 at 7:35 PM
Is this fixed in VS 2012 Update 1?
Posted by Andrew Ritz on 8/13/2012 at 7:26 AM
Color me crazy, but aren't "high priority" and "backlog" two conflicting concepts?
Posted by Microsoft on 8/9/2012 at 9:23 PM

I have created a high priority user story to track this request. I am resolving this bug as Copied to backlog.

Mathew Aniyan
Program Manager - Visual Studio ALM.
Posted by Microsoft on 6/26/2012 at 9:32 PM

Thanks for the clarification. We are working on fix for this.

Mathew Aniyan
Program Manager - Visual Studio ALM.
Posted by Andrew Ritz on 6/26/2012 at 4:45 AM
I'm not reporting on not being able to get to a stack trace at all. The bug is that the test runner will crash, and test explorer will give invalid feedback (the test is listed as 'not run' when it should be 'failed' in this case). Basically the behaviour is inconsistent with other exceptions that are thrown during a test, and I feel that they should be handled in the same manner.
Posted by Microsoft on 6/26/2012 at 12:35 AM

When the crash happens, there is an error message shown in the Output Window, which shows how to enable dumps. After updating the registry as per these instructions, if you rerun the test, you will get a link to the dump file in the Output window. The dump file will show the full stack trace and help you debug.

Were you able to discover this workflow?
Are there any reasons for not using this workflow?

Mathew Aniyan
Program Manager - Visual Studio ALM.
Posted by Andrew Ritz on 6/8/2012 at 7:30 AM
If this is actually a duplicate, it would be nice if you could mention what it is a duplicate of. I am still interested in the topic you know.
Posted by Microsoft on 5/24/2012 at 10:12 PM
Thanks for your feedback and reporting issue.

We made a note of issue and working on fixing the scenario for future builds.

Visual Studio Product Team
Posted by MS-Moderator10 [Feedback Moderator] on 5/22/2012 at 10:06 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by MS-Moderator01 on 5/22/2012 at 10:43 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(
Posted by Andrew Ritz on 5/22/2012 at 10:06 AM
Now that I think about it, this is also a problem in Visual Studio 2010.