Hi

not sure if this is still active... it's the most recent reference to similar problems I found on the forum, the others being:
https://forum.processing.org/topic/glgraphics-glexception-surface-already-locked
https://forum.processing.org/topic/second-window-for-drawing-controls-glgraphics-not-working

I was wondering if this was ever resolved. I too am having problems receiving the same error code while using GLTextureWindow and GLGraphicsOffScreen objects. I'm also using GS video and trying to get two unframed windows working fullscreen on different monitors, with one rendering a video stream and the other featuring 3d content.

I tried using the main PApplet window for 3d content and the GLTextureWindow for the video stream and vice versa, always resulting to what appear as random crashes (sometimes it works for some reason (!) -- I kind of have associated this with just reordering pieces of code or tweaking the video card settings, but it could be that I'm just becoming superstitious).

I've tried Processing 1.2.1 and 1.5.0 both in 32-bit mode and in 64-bit expert mode (using Java 1.7) always using GLGraphics 1.0.0 and GSVideo 1.0.0
It keeps producing inconsistent results, so I can't rule out anything (sometimes it works, sometimes it doesn't)

FYI, I'm on an XP x64 machine and a Quadro FX 1800 on 270.71 drivers.

any advice would be most welcome


@andres, in any case, thank you for these great libraries!

Hi andres

Thanks for the very quick reply. Much appreciated!

about the threading issue, should I be seeing two java***.exe processes in the task manager (corresponding to each window) or the threads are internal to the java process? I only see one.

I've been doing more tests, but results are still inconsistent. It's always the GLTextureWindow that crashes while the main PApplet one runs fine, regardless of which window I use for video streaming through GSVideo and for 3d content. I've tried reordering parts of the code in setup(), like other forum members had suggested and focusing on where the declaration of the GL stuff happens, but I can't pin it down to any specific issue. I've also tried to make all drawing calls in the main window using a this.xxxxxx prefix, which seems to help, but I can't be sure. One thing I've noticed is that once a first crash is produced, all consequent runs of the script produce crashes. Also, in the event that the script runs well and I quit it and rerun it very fast, it's more likely to have a crash. Could it be something like the video card memory/buffer doesn't get cleared well enough between consequent runs?  I think that I can reduce the number of crashes when I'm starting Processing 1.2.1 with the normal processing.exe and not with a nodirectdraw.exe that I've normally been using in order to avoid getting some artifacts in the Processing IDE. This doesn't seem to have an effect in Processing 1.5.0 and 1.5.1, though and I can't be too certain about this as it's also inconsistent.

At the moment I'm considering trying to use a spare Geforce GTS 450 that I have, just in case it's some combination with the Quadro FX 1800 and its drivers. Do you think that this problem is not generated in the Mac OS? If this is so, I could try to arrange for a Mac for the presentation of this project.

I'm a little frustrated about this, because initially I was trying to do it using two PApplets and two borderless Frames, but I was also having some trouble with this as I wanted to use GLGraphics for acceleration of GSVideo (I'm streaming HD 1080 video clips that are chained -- another issue that I had finally managed to solve) and I couldn't easily get both windows to use OpenGL (that I also need for the 3d content). Then I discovered the GLTextureWindow class and your example for having two GL windows and suddenly life became much easier! I hope I can make this work or at least significantly reduce the amount of crashing, or I will have to get back to trying to make the other alternative work.

Btw, I have another question, in case the problem gets resolved. Does the GLTextureWindow have its own PApplet or is it a kind of extension of the main one? The reason I'm asking is because I was also planning to use the PeasyCam library, where the Peasycam camera class needs to be fed the parent PApplet as a reference in the construction (in most cases "this"). Is there any chance I can make a similar reference to the GLTexture window if I use one for the 3d content?

Anyway, thanks again. I will get back if I have any results.


EDIT:
Changing the graphics card and using the 285.58 drivers didn't have any effect.

I played more with the code and it occured to me that it might be that overloading the graphics card with too many OpenGL calls in setup() might be a possible reason for the problems. I tried taking out as much as I could from setup and putting it in draw(), while attempting to stop things from happening simultaneously. So, I used some ugly framecount checks to make the initial OpenGL calls. I also let a time lapse of 100 frames before starting to draw anything at all in the main window. Apparently, this cheap workaround seems to improve things significantly. It ensures that the movie is first read, then loaded into an offscreen buffer texture and consecutively displayed on the GLtexture window (with some frames lapsing in between). After the movie starts being rendered, the 3d stuff start getting rendered in the main window.

This does not cure the situation entirely - crashes still happen occasionally - but it will have to do for now.

Also, Andres, do you thing that any of the graphics card settings (antialiasing, texture filtering, triple buffering, threaded optimisation etc) might have any effect?

thanks