Hi! Thanks for sharing this issue. It is not normal for this process to guzzle threads, although this is the same process that is used to execute your test code, so if you have a test (or series of tests) that create suspended threads, then this is certainly possible.

Try connecting to the process using the Visual Studio debugger and examine the call stack of the executing threads. Do they have anything in common?