GLException: Attempt to make the same context current twice on thread

Today I switched over to the new 0.7 version of Xith, and downloaded the latest JOGL jar file, and then changed my import to use JSR231 for rendering. I had no problems before, but now I am getting the following exception. Any ideas on what is causing this?

Exception in thread "main" javax.media.opengl.GLException: javax.media.opengl.GLException: Attempt to make the same context current twice on thread Thread[AWT-EventQueue-0,6,main]
	at javax.media.opengl.Threading.invokeOnOpenGLThread(Threading.java:266)
	at javax.media.opengl.GLCanvas.maybeDoSingleThreadedWorkaround(GLCanvas.java:256)
	at javax.media.opengl.GLCanvas.display(GLCanvas.java:130)
	at com.xith3d.render.jsr231.CanvasPeerImpl.render(CanvasPeerImpl.java:1207)
	at com.xith3d.scenegraph.View.renderOnce(View.java:616)
	at com.xith3d.scenegraph.View.renderOnce(View.java:549)
	at net.zeromatrix.rpg.toolkit.mapeditor.GUI.run(GUI.java:1185)
	at net.zeromatrix.rpg.toolkit.mapeditor.GUI.<init>(GUI.java:824)
	at net.zeromatrix.rpg.toolkit.mapeditor.MapEditor.<init>(MapEditor.java:27)
	at net.zeromatrix.rpg.toolkit.mapeditor.MapEditor.main(MapEditor.java:11)
Caused by: javax.media.opengl.GLException: Attempt to make the same context current twice on thread Thread[AWT-EventQueue-0,6,main]
	at com.sun.opengl.impl.GLContextLock.lock(GLContextLock.java:83)
	at com.sun.opengl.impl.GLContextImpl.makeCurrent(GLContextImpl.java:115)
	at com.sun.opengl.impl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:182)
	at javax.media.opengl.GLCanvas$DisplayOnEventDispatchThreadAction.run(GLCanvas.java:298)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)
Exception in thread "AWT-EventQueue-0" javax.media.opengl.GLException: Attempt to make the same context current twice on thread Thread[AWT-EventQueue-0,6,main]
	at com.sun.opengl.impl.GLContextLock.lock(GLContextLock.java:83)
	at com.sun.opengl.impl.GLContextImpl.makeCurrent(GLContextImpl.java:115)
	at com.sun.opengl.impl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:182)
	at javax.media.opengl.GLCanvas.maybeDoSingleThreadedWorkaround(GLCanvas.java:258)
	at javax.media.opengl.GLCanvas.display(GLCanvas.java:130)
	at javax.media.opengl.GLCanvas.paint(GLCanvas.java:142)
	at sun.awt.RepaintArea.paintComponent(Unknown Source)
	at sun.awt.RepaintArea.paint(Unknown Source)
	at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source)
	at java.awt.Component.dispatchEventImpl(Unknown Source)
	at java.awt.Component.dispatchEvent(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

I have the same problem.

Really, no idea. I switched myself to JSR-231 long before I made the release, and I never had this problem.
Probably c_lilian can help us there…

I’ve narrowed the problem down to something related to running inside a GUI. I have a separate application that just loads a tile map fullscreen and it seems to run fine using JSR-231. sialivi, I will let you know if I find anything else out…

I think I just inadvertently figured out what was wrong. After I went back and tried my GUI application, it worked fine. I had forgotten to download the latest jogl*.dll files (from the jogl-natives-windows-i586.jar), so you may want to try that if you don’t have the most recent ones.

Ah silly me, I forgot to tell in the Releases notes you had to grab the latest binaries too.
Anyway, this will be fixed in Xith 0.7.1 (soon released).