You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I execute all tests of one test assembly. This assembly contains 5000 unit tests which are running pretty fast.
If I first click 'Stop' running tests and afterwards 'Kill' running tests, the application shows this information message, but stops to respond at all to all user actions. It seems that the application is freezed and it doesn't recover from this state.
Ultimately the only option is to kill the application itself.
That's the information message which is shown:
To Reproduce
Steps to reproduce the behavior:
I assume that this issue is related to some threading issue, so naturally these steps will not work always reliable.
When attaching a debugger to this use case, I notice that it seems to be a deadlock issue between two threads.
The main thread is currently taking care that the test run is killed. For that purpose it turns to the TestCentric.Engine. Here's the callstack:
On the other hand there's a test event currently processed, which wants to update a TreeNode image according to the test result. For that purpose it needs to invoke the Main Thread. Here's the callstack from that thread:
So overall I assume that both threads are waiting for each other, resulting in the deadlock
In addition here are the callstacks including the TestCentric.Engine parts. They complement the previous observation. First screenshot is the main thread:
And this is the corresponding code:
And that's the callstack from the TestEvent thread:
And here's the corresponding code:
Describe the bug
I execute all tests of one test assembly. This assembly contains 5000 unit tests which are running pretty fast.
If I first click 'Stop' running tests and afterwards 'Kill' running tests, the application shows this information message, but stops to respond at all to all user actions. It seems that the application is freezed and it doesn't recover from this state.
Ultimately the only option is to kill the application itself.
That's the information message which is shown:
To Reproduce
Steps to reproduce the behavior:
I assume that this issue is related to some threading issue, so naturally these steps will not work always reliable.
=> Appication gets freezed
Sample test project.zip
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: