ReSharper Unit Test Runner Crash

I'm trying to run the unit tests in an assembly containing just over 1,400
tests and ReSharper's unit test runner consistently crashes with
StackOverflowException. As reported previously, the only way to obtain any
exception information is to click the Debug icon; otherwise, ReSharper just
eats the exception and pretends nothing happened. I copied as much of the
call stack as I could, but the exception detail isn't much help... it just
says "Cannot evaluate expression because the current thread is in a stack
overflow state." And yes, these unit tests ran fine with prior versions of
ReSharper.


JetBrains.ReSharper.UnitTestProvider.MSTest.dll!JetBrains.ReSharper.UnitTestProvider.MSTest.MSTestTaskRunnerRecursive.RunTests(JetBrains.ReSharper.UnitTestProvider.MSTest.MsTestTestAssemblyTask
task = {JetBrains.ReSharper.UnitTestProvider.MSTest.MsTestTestAssemblyTask})
Line 123 + 0x50 bytes C#
JetBrains.ReSharper.UnitTestProvider.MSTest.dll!JetBrains.ReSharper.UnitTestProvider.MSTest.MSTestTaskRunnerRecursive.ExecuteRecursive(JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNodenode
= {JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode}) Line 60C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.Execute(JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode
node ={JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode}) Line 103
+ 0xbbytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.DoExecuteNodes(System.Collections.Generic.IEnumerable<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode>
nodes =Count = Cannot evaluate expression because the current thread is in a
stackoverflow state.) Line 68 + 0x32 bytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.ExecuteNodes(System.Collections.Generic.IList<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode>
nodes = Count =Cannot evaluate expression because the current thread is in a
stack overflowstate.) Line 54 C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskRunnerHostBase.ExecuteSerializedTree(string
serializedTree)Line 33 C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.IsolatedAppDomainHost.ExecuteNodes(System.Collections.Generic.IList<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode>
roots = Count =Cannot evaluate expression because the current thread is in a
stack overflowstate.) Line 78 C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.IsolatedAssemblyTaskRunner.ExecuteRecursive(JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode
node ={JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode}) Line 44 +
0x1ebytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.Execute(JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode
node ={JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode}) Line 103
+ 0xbbytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.DoExecuteNodes(System.Collections.Generic.IEnumerable<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode>
nodes =Count = Cannot evaluate expression because the current thread is in a
stackoverflow state.) Line 68 + 0x32 bytes C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.CurrentAppDomainHost.ExecuteNodes(System.Collections.Generic.IList<JetBrains.ReSharper.TaskRunnerFramework.TaskExecutionNode>
nodes = Count =Cannot evaluate expression because the current thread is in a
stack overflowstate.) Line 54 C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskExecutor.Run(string
remotingAddress
="ipc://fe8fe565-debe-4faf-a80b-7c08ec1d19d6/0d9465d1-ef75-47ee-b617-af0d36153555;fe8fe565-debe-4faf-a80b-7c08ec1d19d6",
string sessionID ="ad46e809-196a-4774-bc20-b585ac9da3cf", bool
isolateAssemblies =
true,JetBrains.ReSharper.TaskRunnerFramework.ProxyFactoryDelegate
proxyFactory ={Method = Cannot evaluate expression because the current
thread is in astack overflow state.}) Line 87 C#
JetBrains.ReSharper.TaskRunnerFramework.dll!JetBrains.ReSharper.TaskRunnerFramework.TaskExecutor.Run(string
remotingAddress
="ipc://fe8fe565-debe-4faf-a80b-7c08ec1d19d6/0d9465d1-ef75-47ee-b617-af0d36153555;fe8fe565-debe-4faf-a80b-7c08ec1d19d6",
string sessionID ="ad46e809-196a-4774-bc20-b585ac9da3cf", bool
isolateAssemblies = true) Line29 C#
JetBrains.ReSharper.TaskRunner.exe!JetBrains.ReSharper.TaskRunner.TaskRunnerApplication.Main(string[]
args = {string[2]}) Line 44 + 0x36 bytes C#


8 comments

I have exactly the same problem, any solution on this problem?

0

See http://www.jetbrains.net/jira/browse/RSRP-100311

Should be fixed in next available nightly build (1253).

Please tell me, if it helps or not.

0

Could you provide some details on how do you run your tests:

  1. How many tests do you execute at once?
  2. How many classes contain those tests?
  3. Do you execute all tests in assembly or select some of them?
0
  1. How many tests do you execute at once?
    1. 1144
  2. How many classes contain those tests?
    1. About 218
  3. Do you execute all tests in assembly or select some of them?
    1. I am running the macro Resharper.Resharper_Unitest_RunSolution


My solution contains of 14 project where 4 project are unittest projects

0

Another attempt to fix this issue is made in build 1258.

It works and works very fast on my project with 1500 tests.

0

Victor Kropp wrote:

Another attempt to fix this issue is made in build 1258.

It works and works very fast on my project with 1500 tests.

---
Original message url:
http://www.jetbrains.net/devnet/message/5240084#5240084


Build 1258? Latest build i found is 1256. Can you correct which build
number?

--
by Peter Sulek at 16. 6. 2009 9:01:42
XanaNews 1.18.1.6

0

Sorry, next public nightly build is postponed due to some other issues. It will have number 1257, I guess. Should be released in a few days.

0

Have tried with 1258. And now it is working.

0

Please sign in to leave a comment.