| Error Transition from COM context |
|
| Written by Administrator | |
| Thursday, 23 September 2010 05:39 | |
Error Transition from COM contextWhen debugging .NET Application using Microsoft Visual
Studio, sometimes It appears an error like this below : "The CLR has been unable to transition from COM context 0x212c28 to COM context 0x212d98 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."
This occurs
when using a Debugger.Break statement in my Win Form code while
demonstrating examples during a workshop. To fix for the problem is to go
to the Debug -> Exceptions -> Managed Debug Assistants menu in
Visual Studio and uncheck the ContextSwitchDeadlock
I
already knew about this Managed Debugging Assistants checkbox and
had unchecked it in the past. The big revelation for me was that
this setting is saved in the abc.suo file and is not a global Visual Studio
setting. That means I have to remember to change this for every project I
made !
|
|
| Last Updated on Thursday, 23 September 2010 06:00 |
List All Products |
|
|
Advanced Search |
|
| Lost Password? | |
| Forgot your username? | |
|
|
|
| Download Area |