in

C1 Community

ComponentOne Community is a free source for developers and help authors to collaborate and communicate.

ContextSwitchDeadlock was detected

Last post 04-17-2008 1:54 AM by C1_JohnAd. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-15-2008 3:13 AM

    ContextSwitchDeadlock was detected

    I'm simply Binding TrueDBGrid with dataset which has datalibrary in desing time. but as soon as i execute project subject error thrown by CRL.

    Error Details

    The CLR has been unable to transition from COM context 0x1a10b8 to COM context 0x1a1228 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.

     

    Adnan Memon
  • 04-17-2008 1:54 AM In reply to

    Re: ContextSwitchDeadlock was detected

    Hi Adnan,
     
    I have attached a small sample in which C1TrueDBGrid is bound to a custom object. Please take a look and see if this helps. In case if not then please make some necessary changes or is possible please post a small sample which can reproduce the said behavior. Please let me know which version of C1TrueDBGrid you are using.
     
    Regards,
    John Adams
     

    I'm simply Binding TrueDBGrid with dataset which has datalibrary in desing time. but as soon as i execute project subject error thrown by CRL.

    Error Details

    The CLR has been unable to transition from COM context 0x1a10b8 to COM context 0x1a1228 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.

     


    Adnan Memon

    http://helpcentral.componentone.com/cs/forums/p/74955/203852.aspx#203852

Page 1 of 1 (2 items)
Contact ComponentOne: 1.800.858.2739 ©1987-2008 ComponentOne LLC All Rights Reserved.