Hi Whilst debugging my program in VS 2008 I have come across the following error: The CLR has been unable to transition from COM context 0x34fc1a0 to COM context 0x34fc258 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 wi...
Hello, I have a strange error: Managed Debugging Assistant 'ContextSwitchDeadlock' has detected a problem in 'C:\Documents and Settings\Lena G\My Documents\SchoolStuff\IR Information\Home Work\FianlProject\finalProject\finalProject\bin\Debug\finalProject.vshost.exe'. Additional Information: The CLR has been unable to transition from CO...
Any creative ideas to avoid deadlocks on a yield or sleep with cooperative/non-preemptive multitasking without doing an O/S Thread.Sleep(10)? Typically the yield or sleep call will call back into the scheduler to run other tasks. But this can sometime produce deadlocks. Some background: This application has enormous need for speed and,...
Hello everyone, I'm facing an extremely weird bug here and I'm not really sure If I'm following the right path to solving it or even how to solve it. Here is the problem I'm facing: I start debugging a WPF application which uses log4net, NHibernate and LINQ to NHibernate, and when I try to get an Entity from the database my application...
I have a system consisting of two parts: WCF server (console) and client (WinForms). Server publishes a service for remote access to the database, and client connects. Everything runs smoothly, client is able to read database documents, attachments and so forth. However, after 60 seconds running in debugger, the following client problem ...
So I'm running a unit test, it's a "bad" unit test which takes a LONG time to run. (which used to work just fine) Now I'm getting the Context switch deadlock Detected error, I'm guessing because it's such a long process (20 min) to do the whole test. Much like described here: http://bytes.com/topic/c-sharp/answers/471705-context-switch...