Hi Chris,

I'm sorry to say that this is not likely to be NCrunch's fault. NCrunch's integration with the debugger is a few minimal lines of boilerplate code, where we tell it to attach to a process, or to detach at the end of a test run.

The debugger is an extremely complex beast and I've observed issues like the one you've described both come and go over the years. I suggest checking to make sure you have all the latest VS updates installed.

There are differences in behaviour when using NCrunch compared with other runners.

When using the debugger, NCrunch first launches the process, then attaches to it. When the test run completes, NCrunch detaches and then terminates the process later.

Most other runners will launch the process with the debugger already attached, and will let it run until the test run completes. They then terminate the process and the debugger automatically detaches.

Probably there is something in NCrunch's workflow that triggers the issue inside the debugger.

Something you can try is changing the way you complete your debug session. After you have the information you need from the debugger, try terminating the process in VS instead of letting the debugger run and the test complete. This should give you an alternative workflow that will hopefully prevent the IDE from becoming unstable.

I appreciate how frustrating this problem is. I have a special swear jar for debugger related issues. The worst thing about them is their timing - they tend to appear when you're neck deep in a problem with everything set up just right.