Error in windows application: long running operation without pumping Windows messages

Question

0.00/5 (No votes)

See more:

Hi All,

I am having an application wherein I am getting an error

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

My application is in VB.NET windows based.

In my application I have used a thread that run continuously and at some point of time it gives me this error.

For this issue I unchecked visual studios "DEBUG->Exceptions->Managed Debugging Assistant(MDA)" here under THROW column I have unchecked "DisconnectedContext" and "ContextSwitchDeadlock". But still not able to detect the main problem....

Please suggest if any

Posted 11-Oct-13 3:25am

Phionix11

Updated 10-Oct-20 3:51am

v2

Add a Solution

3 solutions

Solution 2

How to use "CoWaitForMultipleHandles" ?[^]

It seems that it is just a feature of a debugger, and if you turn it off, it will not break any more.

I just found this, and it worked for my VB.NET console application (although I do not understand what is connection between a "message pump" [which sounds so windows-ly) and a console application).

Posted 26-Feb-20 23:07pm

Gjuro Kladaric

Solution 3

I already faced this error message.
I read about the solutions concerned this message here: https://social.msdn.microsoft.com/Forums/office/en-US/320459e9-7247-41a2-a24e-7eda359b2686/contextswitchdeadlock-occurred?forum=csharpgeneral

Open "Exception Settings" (Ctrl+Alt+E)
Under "Managed Debugging Assistants"
We need to do uncheck "ContextSwitchDeadlock" It can solve this error.

With Regards.
KWN

Posted 10-Oct-20 3:51am

Member 11969558

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2013-10-11T03:49:00

Solution 1

I've seen this before and found that it is an error that only shows up when your app is running under the the Debug build under the debugger. The Release build running outside Visual Studio will never show this problem at all.

Posted 11-Oct-13 3:49am

Dave Kreskowiak

Comments

tnashc 8-Oct-14 12:58pm

My app gave me that error even when I ran it in release mode.

Dave Kreskowiak 8-Oct-14 13:16pm

If you run it under the debugger, it will throw this message. If you run the Release outside of Visual Studio, it doesn't happen.