Home » Discussion forums » OpenTK » Development
tksuoran's picture

SVN: The CLR has been unable to transition...

Posted Friday, 5 November, 2010 - 23:22 by tksuoran in

I got OpenTK from SVN to resolve couple of issues. Now my app starts fine but after maybe 1 minute I get this:

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

‹ X11GLContext could check for driver version? WPF OpenGL interop revisited with WGL_NV_DX_interop ›

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
the Fiddler's picture

Re: SVN: The CLR has been unable to transition...

Posted Saturday, 6 November, 2010 - 00:15 by the Fiddler

Try removing the [STAThread] attribute from your main method.

tksuoran's picture

Re: SVN: The CLR has been unable to transition...

Posted Saturday, 6 November, 2010 - 09:31 by tksuoran

Thanks, that helped. Any insight why this change was needed?

tksuoran's picture

Re: SVN: The CLR has been unable to transition...

Posted Saturday, 6 November, 2010 - 09:31 by tksuoran

Thanks, that helped. Any insight why this change was needed?

the Fiddler's picture

Re: SVN: The CLR has been unable to transition...

Posted Saturday, 6 November, 2010 - 10:23 by the Fiddler

Apparently, the managed debug assistant doesn't like the message pump in OpenTK. Messages *are* being pumped (otherwise your application would have locked up) so I am not sure why this is happening. Things appear to work fine when running outside Visual Studio, too.

If someone has any ideas, do tell.

A "short" introduction to the COM appartment model and how it affects the CLR. It's a huge and complicated subject.