Posted by Sven Gothel on Jan 10, 2013; 7:51pm
URL: https://forum.jogamp.org/jogl-crashes-video-card-driver-tp4026980p4027785.html

On 01/10/2013 05:38 PM, runiter [via jogamp] wrote:
> great, it now works on both Intel and non-Intel machines.
>
nice.

> How there is still that annoying exception. In stand-alone there is not
> exception, but in webstart I get this exception even though it renders fine:
>
> Catched: Context not current on current thread AWT-EventQueue-0:
> WindowsOnscreenWGLContext [OpenGL 3.3, options 0x303, 3.3 (Compatibility
> profile, arb, ES2 compatible, FBO, hardware) - 3.3.0, this 0x13be76d, handle
> 0x20000, jogamp.opengl.gl4.GL4bcImpl@1309b8c,

<snip/>

>         surfaceLock <3405f6, 17390f9>[count 0, qsz 0, owner <NULL>]]]]
>         at jogamp.opengl.GLContextImpl.release(GLContextImpl.java:279)
>         at jogamp.opengl.GLContextImpl.release(GLContextImpl.java:272)
>         at jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:919)
>         at jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:822)
>         at javax.media.opengl.awt.GLCanvas$7.run(GLCanvas.java:1028)

Looks like an imbalance of makeCurrent/free calls here
induced by a GLEventListener, since the offending 'release' call
of GLDrawableHelper.invokeGLImpl(..) has it's matching makeCurrent()
in the same code block. So it must have been released before by a
GLEventListener - or the AutoDrawable display method, IMHO.

~Sven