ContextSwitchDeadlock during scheduler DataSource setting

2 posts, 0 answers
  1. Dejo Savicevic
    Dejo Savicevic avatar
    10 posts
    Member since:
    Apr 2010

    Posted 20 Aug 2010 Link to this post


    We have scheduler with resources. When try to set scheduler DataSource property, VS shows the message that ContextSwitchDeadlock was detected. DataSource contains 1 resource with more than 200 appointments. I guess the problem is in a large number of appointments we try to show. Is there any limits regard this. This is a complete text of a message:
     ContextSwitchDeadlock was detected
    Message: The CLR has been unable to transition from COM context 0x20cae8 to COM context 0x20cc58 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.


  2. Jack
    Jack avatar
    2333 posts

    Posted 26 Aug 2010 Link to this post

    Hi Dejo Savicevic,

    Thank you for contacting us. Yes in the past we had issues when using a large number of appointments. We believe that the issue is addressed in our latest release - Q2 2010 SP1. I noticed that you have downloaded an old version of RadControls for WinForms. I recommend that you try the latest one and share your feedback. We will appreciate that.

    If the issue continues to appear, please send us your application so we can test and locate the issue. 

    I am looking forward to your reply.

    Kind regards,

    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top