Blog

Share this blog : twitter

Oct 30

Written by: IOTAP ::-- DotNet Team
10/30/2008 5:02 PM 

I was facing problem  with "ContextSwitchDeadlock" exception showing up  while debugging an windows application.The exception was a frustrating one.

I was facing problem  with "ContextSwitchDeadlock" exception showing up  while debugging an windows application.The exception was a frustrating one.

Following is the message i was getting

ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x1a2a28 to COM context 0x1a2b98 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 was wondering about the logics that used in the program finally i found out the solution.Thanks to Scott Munro.

You can solve it by switching Managed Debug Assistant  OFF by typing the  shortcut  Ctrl +Alt + E  (Yet to find the direct menu  )  and unchecking corresponding exception.

 

Tags:

Your name:
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Security Code
Enter the code shown above in the box below
Add Comment   Cancel 


 
 
 

IOTAP is an IT Consulting and Software Services Company with global delivery centers in Mumbai and Chennai, India. We are a Microsoft Gold Certified Partner and use products and technologies like Dynamics CRM, SharePoint, Silverlight, and the .Net platform to create solutions that help our customers connect, communicate and collaborate effectively