Visual Studio 2005/2008/2010: ContextSwitchDeadlock was detected Message (via Keith Barrows)
Posted by jpluimers on 2010/07/27
Like Keith Barrows, each time I see a message like below, I’m reminded that I forgot to change my Visual Studio 2005/2008/2010 to disable these kinds of MDA messages:
ContextSwitchDeadlock was detected Message: The CLR has been unable to transition from COM context 0x1a7728 to COM context 0x1a75b8 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.
Steps to get rid of these messages:
- Start Visual Studio :-)
- In the menu, select “Debug”; “Exceptions…” (Ctrl-D, E)
- Open the “Managed Debugging Assistants” tree
- Uncheck the first checkbox in the “ContextSwitchDeadlock” row
Maybe I won’t forget this next time :>
–jeroen
Via: Keith Barrows : ContextSwitchDeadlock was detected Message.
The Wiert Corner - irregular stream of stuff 
Kumari Sony said
Simply select Exceptions from the Debug menu in the visual studio 2005 window , the Edxception Dialog box wil popup , select the Managed Debugging Assistants Exception Node , then select ContextSwitchDeadlock and remove the select from Thrown column . this will stop the vs from throwing the ContextSwitchDeadlock exception.