The previous post found a deadlock by asking which thread owned which monitor. This one has the same symptom, a process that hangs and uses no CPU, and none of that evidence: no monitor is held, no thread is contended, and the thread pool is idle. It is the classic .Result deadlock, and finding it from a dump means following a completely different trail. The sample contains the application, the collection… [read more]