Re: ContextSwitchDeadlock Problem
- From: Kalpana <kalpana@xxxxxxxxxx>
- Date: Tue, 13 Feb 2007 04:08:27 -0800
It is not working.
Is there is any chance of having this problem due to the handles invoked
from WndProc()?
Previoulsy i had a problem with Utilitylibrary.Rebar --> WndProc()
recursive call (deadlock). I posted this problem but no one reply --> so
for the temporary survive i kept a condition for termination (to avoid
deadlock). condition is:
if (m.Msg == (int)Msg.WM_WINDOWPOSCHANGED)
return;
if condition reaches then control will be returned from WndProc().
Is this present problem of flickering (when we don't debug) and
ContextSwitchDeadLock exception --(when we debug -- see the exception
below) is due to WndProc() condition??
However please suggest
EXCEPTION DESCRIPTION:
The CLR has been unable to transition from COM context 0x1a0768 to COM
context 0x1a08d8 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.
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: ContextSwitchDeadlock Problem
- From: Willy Denoyette [MVP]
- Re: ContextSwitchDeadlock Problem
- Prev by Date: Re: DLLImport for C lib
- Next by Date: Looking for a good screen report free library
- Previous by thread: ContextSwitchDeadlock Problem
- Next by thread: Re: ContextSwitchDeadlock Problem
- Index(es):
Relevant Pages
|
