C# – Pumping Windows Messages During Long Operation

cmessage-pump

I'm getting the following message on a big operation that I'm running:

The CLR has been unable to transition
from COM context 0x1fe458 to COM
context 0x1fe5c8 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.

How do I send windows messages so that this error will no longer occur on long operations?

Best Answer

It's unclear exactly what the context is - are you performing some long-running task on the UI thread of a WinForms or WPF app? If so, don't do that - use BackgroundWorker, or run the task on the thread pool or a new thread directly (possibly using Control.Invoke/BeginInvoke or Dispatcher if you need to update the UI). If your big operation uses the COM component which is complaining, it'll be harder...

Related Solutions

C# – Visual Studio: ContextSwitchDeadlock

The ContextSwitchDeadlock doesn't necessarily mean your code has an issue, just that there is a potential. If you go to Debug > Exceptions in the menu and expand the Managed Debugging Assistants, you will find ContextSwitchDeadlock is enabled.

If you disable this, VS will no longer warn you when items are taking a long time to process. In some cases you may validly have a long-running operation. It's also helpful if you are debugging and have stopped on a line while this is processing - you don't want it to complain before you've had a chance to dig into an issue.

C# – problem with searching subdirs

The GetFiles method has an override that allows for recursive searching. I would try using that and see if your problem goes away...

void DirSearch(string sDir)
{
    try
    {
        var files = System.IO.Directory.GetFiles(sDir, "*.*", SearchOption.AllDirectories);
        foreach (string f in files)
        {
            string hash = GetMD5HashFromFile(f);
            Dic_Files.Add(f, hash);
        }
    }
    catch (System.Exception excpt)
    {
        Console.WriteLine(excpt.Message);
    }
}

Best Answer

Related Solutions

C# – Visual Studio: ContextSwitchDeadlock

C# – problem with searching subdirs

Related Topic