search

hyyly / csexwb2

Automatically exported from code.google.com/p/csexwb2
0 stars 0 forks source link

runtime error MDA #91

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

Sometimes i'm getting this error:

Managed Debugging Assistant 'ContextSwitchDeadlock' has detected a problem
in 'C:\Users\User\Documents\Visual Studio
2008\Projects\TestProject\TestProject\bin\x86\Debug\TestProject.vshost.exe'.
Additional Information: The CLR has been unable to transition from COM
context 0x546960 to COM context 0x546b88 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.

I'm running a multithreaded application, with 4 webbrowsers.

IE = 8
OS = vista x64

Original issue reported on code.google.com by A.Bouchl...@gmail.com on 14 Mar 2010 at 11:31

GoogleCodeExporter commented 9 years ago 

My app grows really big at runtime. I think there is a memory leakage..

Original comment by A.Bouchl...@gmail.com on 14 Mar 2010 at 2:46

GoogleCodeExporter commented 9 years ago 
I get this same issue, though I am not multithreading.  I create a single 
instance of
the cEXWB object and about 60 seconds later I get the MDA message.

Original comment by thebrentster on 16 Apr 2010 at 10:57

GoogleCodeExporter commented 9 years ago 
Same error.

WinXP Home Premium 32bit
IE8
VB.Net 2005 and VB.Net 2008
CSWbEx version 2.0.0.2
ComUtilities Version 1.0.0.1

Single instance browser.  Ignored the MDA message and after message would 
typically 
fire, browser goes unresponsive as if using a wireless connection and you 
disable the 
wireless radio, but continue to use the browser.  Control throws NavgateError 
event.

During event, tried disposing control and setting control to new instance with 
no 
result.  Control will not navigate once MDA is thrown.

Original comment by aparsons...@gmail.com on 20 May 2010 at 5:53

GoogleCodeExporter commented 9 years ago 
I the same problem - running on:

Windows Vista 32 Bit
IE8
VS 2008 SP1
CSWBEx 2.0.0.2
ComUtilities 1.0.0.1
Running Single instance Browser in STA mode

Original comment by tommy.bi...@gmail.com on 15 Jul 2010 at 1:40

GoogleCodeExporter commented 9 years ago 
Just to add to the above comment.

I experience the same problem with the csexwb demo application.
Still running on VS 2008.

Original comment by tommy.bi...@gmail.com on 15 Jul 2010 at 2:03

GoogleCodeExporter commented 9 years ago 
I find that the MDA messages only appear when you are running nder the IDE. If 
you run your apps outside the IDE, the problem isnt there. I have  seen this 
happen under other long running controls that are really 'wrapped COM'.

Original comment by mwechter1@gmail.com on 15 Aug 2010 at 10:05