Mincus's picture

Debugging under Windows.

Sometimes when I set OpenTK off through the Visual Studio debugger, the window shows stays white and nothing happens.
The only way to get out is to kill the process or stop the program from within Visual Studio.

At first I thought this might be a quirk of my particular set-up (Vista 32-bit, Visual Studio 2005 Professional), but having done a clean reinstall and moved to Visual Studio C# 2008 Express (still under Vista 32-bit), it still seems to be happening.

There's no particular pattern to it, code will work once, no changes, hit F5 again and it'll cause the issue. Kill the process, hit F5 again and it won't happen.

Any ideas? :o/
It's not a huge issue as it only happens once in 20 times and AFAIK only when launched through the debugger, but still would like a resolution.


Comment viewing options

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

I've never encountered this behavior during the 1.5 years I've been working on OpenTK... :) That's on many configurations, too: WinXP + VS2005/VS2008, Vista 32bit + VS2005, Vista 64bit + VS2005/VS2008.

The only reason I can think this could happen is that a breakpoint is hit, which stops WndProc from processing messages. Is this a GameWindow or GLControl application? Also, have you tried with a debug version of OpenTK? It logs a lot of messages to the "output window" in VS.

Has this ever happened outside the IDE? If not, it might be a good idea to search for, and log a bug at http://connect.microsoft.com/VisualStudio/Feedback

Mincus's picture

It's a GameWindow. Not tried a debug version, just been using the DLL in the supplied archive so far.
Shouldn't be a breakpoint, I'm not using any at the moment and as I say it will work completely find on the next launch without me changing _ANYTHING_ in the IDE. I've not seen it happen outside the IDE, but I've not extensively tested anything I've written outside it yet.

Just grabbed the svn, so I'll build a debug version of that, move things on to it and see if this still happens and what (if any) output is given.

teichgraf's picture

I encounter similar things in an almost random period. I use WinXP SP2 and Visual C# 2008 Express.

the Fiddler's picture

This issue looks similar, but is reported as closed in VS2008: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Fee...

Does the problem occur with the plain "quickstart" application? I'm trying to reproduce the issue, to submit a bug report.