Thursday, December 11, 2008

Managed Debugging Assistants - Microst .NET Framework

Symptom:
The CLR has been unable to transition from COM context 0x1a1a90 to COM context 0x1a1c00 for 60 seconds.
The thread that owns the destination context/apartment is most likely either doing a none pumping. 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.


Possible Reasions:

1. Deadlock
2. A very long operation, which worth more than 60 seconds.



Resolution:
If execution does not trap in a deadlock
It is possible to execute an very long operation by Disabling Visual Studio’s MDA (Managed Debug Assistant)
Visual Studio 2005: To disable MDA please add or edit following registry key:

1. Run > regedit
2. Navigate to > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
3. Set [MDA=”0”]
4. Or create MDADisable.reg file and paste following text and run it

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"MDA"="0"

Please note: Always it is useful to leave MDA enable for efficient debugging. To enable MDA please set MDA=”1”


References:
Diagnosing Errors with Managed Debugging Assistants (MSDN)

Azure Storage Account Types

Defferent Types of Blobs Block blobs store text and binary data. Block blobs are made up of blocks of data that can be managed individually...