当我在我的解决方案中运行所有测试（约800个测试）时，经过一段时间后，出现一个带有错误的弹出窗口，显示vstest.executionengine.x86.exe已停止工作。
我得到的一些问题细节的例子如下：
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: vstest.executionengine.x86.exe Problem Signature 02: 14.0.23107.0 Problem Signature 03: 559b7b6c Problem Signature 04: mscorlib Problem Signature 05: 4.6.1076.0 Problem Signature 06: 56d79fa2 Problem Signature 07: 0 Problem Signature 08: ffffffff Problem Signature 09: System.StackOverflowException OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1051 Additional Information 1: 5cd2 Additional Information 2: 5cd2742c12da7dd4b1d5bf900186a452 Additional Information 3: 2fe2 Additional Information 4: 2fe276cacf1c00cd7a2aed7b27f5a5f9 Problem signature: Problem Event Name: APPCRASH Application Name: vstest.executionengine.x86.exe Application Version: 14.0.23107.0 Application Timestamp: 559b7b6c Fault Module Name: clr.dll Fault Module Version: 4.6.1076.0 Fault Module Timestamp: 56d7a0ff Exception Code: c00000fd Exception Offset: 00003567 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1051 Additional Information 1: 0127 Additional Information 2: 01273c850b3b6fc6378d3f666887788e Additional Information 3: 0786 Additional Information 4: 07866ddaac895bff9a7fa791fcdaa4a7在VS输出窗口中，我得到：
------ Run test started ------ The active Test Run was aborted because the execution process exited unexpectedly. To investigate further, enable local crash dumps either at the machine level or for process vstest.executionengine.x86.exe. Go to more details: http://go.microsoft.com/fwlink/?linkid=232477 ========== Run test finished: 0 run (0:03:55,0267906) ==========当我试图启用本地崩溃转储时，我发现没有这样的注册表项，所以我一直无法做到。
我位于所有测试（22测试）导致vstest .---。exe崩溃，评论他们并且再次运行所有测试并且没有那些“错误”测试。 一切运行良好。
这些测试有什么问题？ 他们都是过去工作的旧测试。 如何找到问题？
When I let run all tests (ca. 800 tests) in my solution, after some time a popup window with error is shown that vstest.executionengine.x86.exe has stopped working.
Some Examples of problem details, that I get are here:
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: vstest.executionengine.x86.exe Problem Signature 02: 14.0.23107.0 Problem Signature 03: 559b7b6c Problem Signature 04: mscorlib Problem Signature 05: 4.6.1076.0 Problem Signature 06: 56d79fa2 Problem Signature 07: 0 Problem Signature 08: ffffffff Problem Signature 09: System.StackOverflowException OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1051 Additional Information 1: 5cd2 Additional Information 2: 5cd2742c12da7dd4b1d5bf900186a452 Additional Information 3: 2fe2 Additional Information 4: 2fe276cacf1c00cd7a2aed7b27f5a5f9 Problem signature: Problem Event Name: APPCRASH Application Name: vstest.executionengine.x86.exe Application Version: 14.0.23107.0 Application Timestamp: 559b7b6c Fault Module Name: clr.dll Fault Module Version: 4.6.1076.0 Fault Module Timestamp: 56d7a0ff Exception Code: c00000fd Exception Offset: 00003567 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1051 Additional Information 1: 0127 Additional Information 2: 01273c850b3b6fc6378d3f666887788e Additional Information 3: 0786 Additional Information 4: 07866ddaac895bff9a7fa791fcdaa4a7In VS output window I get:
------ Run test started ------ The active Test Run was aborted because the execution process exited unexpectedly. To investigate further, enable local crash dumps either at the machine level or for process vstest.executionengine.x86.exe. Go to more details: http://go.microsoft.com/fwlink/?linkid=232477 ========== Run test finished: 0 run (0:03:55,0267906) ==========When I tried to enable local crash dumps I found out that there is no such registry key so I haven't been able to do it.
I Located all test (22 tests) causing crash of vstest.---.exe, commented them and run all test again and without those "wrong" tests. Everything runs fine.
What can be wrong with those tests? They all are old tests which was working in past. How to locate a problem?
最满意答案
根据我的经验，StackoverFlowExeptions通常是由一些永不终止的递归方法调用引起的。 尝试调试其中的一个22测试，以确定递归是否是问题。
In my experience, StackoverFlowExeptions are very often caused by some recursive method call that never terminates. Try debugging one of those 22 test to find out if recursion is the issue.
更多推荐
发布评论