VB keeps giving ContextSwitchDeadlock - TechRepublic
General discussion
January 18, 2006 at 07:15 AM
frenchwood

VB keeps giving ContextSwitchDeadlock

by frenchwood . Updated 19 years, 1 month ago

I have a VB program that uploads to Oracle via a CSV file. This all works great, apart from the MDA in Visual Basic 2005 Express keeps telling me the following:

“ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x1a3008 to COM context 0x1a3178 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.”

Any ideas?

This discussion is locked

All Comments