Hi Johan,

I suspect this problem is likely to be related to the code being executed by the test host (i.e. your test code or code under test).

When NCrunch terminates a task runner process, it does so using a hard kill - the same as what you would do if trying to kill the process using task manager. If task manager cannot stop/kill the process, neither can NCrunch.

I recommend taking a look at the activities of this process at the time your test execution run completes. Check particularly for background threads in your code that may be calling into lower level APIs or O/S resources. Ensure that when your tests complete their execution, any state that might hang the process or interfere with its termination has been properly released.

Hi Johan,

Does this only happen when you attach a debugger to the process?

Does it happen consistently?

Do you see it happen on other solutions (i.e. a sample test project with a single empty test)?

Hi Johan,

The VS debugger unfortunately has a history of problems like this ...

MS regularly roll out fixes, but as the problems are often intermittent and environment specific, it's understandably hard to pin them down and resolve them all. The debugger is also subject to other constraints introduced at a low level. It wouldn't be surprised if your SQL transactions were somehow related to this.

NCrunch's integration with the debugger is actually minimal. When requested to run a test with a debugger, NCrunch will launch the test process, then make a call to the IDE to tell it to attach to the process before any test execution begins. When the test execution is complete, NCrunch calls EnvDTE.Process.Detach().

Unfortunately there's very little I can do to help with problems in the debugger itself. Although NCrunch may be surfacing the issue on your system, the workings of the debugger is outside the boundary of what I'm able to troubleshoot.

It may be worth trying a reset of your VS settings to see if this solves the issue - https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3cc5813e-363b-4ab0-85db-5c35ad092aa0/visual-studio-hangs-up-after-stop-debug.