Simon Harriyott

ContextSwitchDeadlock was detected when debugging in Visual Studio 2005

I've been having issues with a "ContextSwitchDeadlock was detected" error message popping up when debugging. The message text is a baffling

The CLR has been unable to transition from COM context 0x197060 to COM context 0x196ef0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

I've read a few things about a config file, but I couldn't get this to work reliably. Instead, you can switch the MDA off by going to:

Debug -> Exceptions -> Managed Debug Assistants

and unchecking the ContextSwitchDeadlock item. Thanks to Scott Munro.

[Tags: ]
17 May 2006