|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Help! pumping wait primitives - what is that?below is the error message I received when about 2/3 of the process is done.
Where in my code I sould look for? Thanks Bill --------- The CLR has been unable to transition from COM context 0x1afa18 to COM context 0x1afb88 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. Bill Nguyen wrote:
Show quoteHide quote > below is the error message I received when about 2/3 of the process is done. You might find this thread useful:> Where in my code I sould look for? > > Thanks > > Bill > --------- > > The CLR has been unable to transition from COM context 0x1afa18 to COM > context 0x1afb88 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. > > <http://groups.google.com/group/microsoft.public.vsnet.debugging/browse_thread/thread/1e4ac1010ae5920d/03ca1c82ea79287b> -- Larry Lard larryl***@googlemail.com The address is real, but unread - please reply to the group For VB and C# questions - tell us which version Larry;
I think you're pointing me to the right direction. However, teh instructions won't help. I created this myProject.mda.config and put in the debug folder. Still got the same error: <?xml version="1.0" encoding="utf-8" ?> <mdaConfig> <assistants> <contextSwitchDeadlock enable="false" /> </assistants> </mdaConfig> Any ideas? Thanks again Bill ContextSwitchDeadlock was detected Message: The CLR has been unable to transition from COM context 0x1afa28 to COM context 0x1afb98 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. Show quoteHide quote "Larry Lard" <larryl***@googlemail.com> wrote in message news:4kb4qlFbd09vU3@individual.net... > Bill Nguyen wrote: >> below is the error message I received when about 2/3 of the process is >> done. >> Where in my code I sould look for? >> >> Thanks >> >> Bill >> --------- >> >> The CLR has been unable to transition from COM context 0x1afa18 to COM >> context 0x1afb88 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. > > You might find this thread useful: > > <http://groups.google.com/group/microsoft.public.vsnet.debugging/browse_thread/thread/1e4ac1010ae5920d/03ca1c82ea79287b> > > > -- > Larry Lard > larryl***@googlemail.com > The address is real, but unread - please reply to the group > For VB and C# questions - tell us which version 
Other interesting topics
Can I make my program more efficient ?
My for each loops do not compile - VB 2003 Can anyone help in shortening this loop??? execution from command line Form2.vb[design] innaccessible ! Run an Access report in a VB .Net application How to detect if program execution is in debug mode? Binding an Image to a picturebox Problem with CustomTyped casting and type checking Encryption: VB 2005 And SQL Server 2005 |
|||||||||||||||||||||||
