ContextSwitchDeadlock

G

Guest

XP box running a Win 2k3 server in a virual PC for CRM development...

Intermittently (once a day ish) when single stepping I get the following
exception:-

The CL context 0x1a19d8 has been unable to transition from COM Context
0x1a1868 to COM context 0x1a19d8 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.
The situation generally has a negative performance impactand may even lead to
the application becoming unresponsive 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.

The code that causes this is nothing special, nothing long running, any ideas?

Guy
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top