I tried running my app today and it came up with a strange error message :
No symbols are loaded for any callstack frame. The source code cannot be displayed."
When I click OK on the message box I get the following :
ContectSwitchDeadlock was detected.
The CLR has been unable to transition from COM context 0x1b1c78 to COM
context 0x1b1de8 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.
I have googled this but to be honest I don't understand any of it.
Can anyone help
I don't understand why this was working not too long ago.
ContectSwitchDeadlock error
Hot Topic
- Get window handle
- Tips on posting
- Multithreading in C#
- Developing Information Collector for the Web
- How to have main program wait for data
- What is the difference between debug mode and release mode?
- Problem in running batch file using C# process
- RichTextBoxScrollBars
- Generic Drive Letter in Server Data Source
- Compiler warning when no other partial class is defined
Visual C#
- Howto loop through attributes of an custom object for generating SqlParameters
- DataGridView - KeyDown and KeyPress events
- Generics class and abstract class
- Delete schedule task and itself...
- use c# .net to open powerbuilder window
- App Config and escape sequences
- SerialPinChange.Break
- PostMessages in to different app using C#
- C# 2.0 closures - bug or feature?
- Syncing data - locking a public property?
ContectSwitchDeadlock error
chris441962
If so:
(1) Go to Debug|Exceptions
(2) Expand "Managed Debugging Assistants"
(3) Untick "ContextSwitchDeadlock".
nosajeel
I am facing the same problem with one of my application. Did you get any solution for this problem.
Thanks
Michael Hansen
I am getting this error logged while running the applicaiton which is built in release mode.
Thanks