Z
Zytan
Make a WebBrowser control, and make a bunch of timers / threads that
continually call WebBrowser.Document.Write. Eventually, this happens:
DisconnectedContext was detected
Message: Context 0x1a1530' is disconnected. Releasing the interfaces
from the current context (context 0x1a13c0).This may cause corruption
or data loss. To avoid this problem, please ensure that all contexts/
apartments stay alive until the applicationis completely done with the
RuntimeCallableWrappers that represent COM components that liveinside
them.
I believe that eventually the WebBrowser takes so long to refresh that
it doesn't complete its job before the next Write, and this occurs.
This explains why it occurs quicker if the Writing speed is increased,
and why it always enivitably happens, even if the writing speed is
slowed. Since, as the page grows in size, the refresh time increases.
Any fixes? It just happens. I can't catch it as an exception.
Zytan
continually call WebBrowser.Document.Write. Eventually, this happens:
DisconnectedContext was detected
Message: Context 0x1a1530' is disconnected. Releasing the interfaces
from the current context (context 0x1a13c0).This may cause corruption
or data loss. To avoid this problem, please ensure that all contexts/
apartments stay alive until the applicationis completely done with the
RuntimeCallableWrappers that represent COM components that liveinside
them.
I believe that eventually the WebBrowser takes so long to refresh that
it doesn't complete its job before the next Write, and this occurs.
This explains why it occurs quicker if the Writing speed is increased,
and why it always enivitably happens, even if the writing speed is
slowed. Since, as the page grows in size, the refresh time increases.
Any fixes? It just happens. I can't catch it as an exception.
Zytan