Application frozen on dispatch_glXMakeContextCurrent0

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Application frozen on dispatch_glXMakeContextCurrent0

Pete
Hello,

I've a strange issue running our JOGL powered app on one of our target platforms, it freezes after running ok for a few minutes.

Here is the trace of where we believe it's stuck - at least as far as the java:

jogamp.opengl.x11.glx.GLX.dispatch_glXMakeContextCurrent0(Native Method)
jogamp.opengl.x11.glx.GLX.glXMakeContextCurrent(GLX.java:768)
jogamp.opengl.x11.glx.X11GLXContext.glXMakeContextCurrent(X11GLXContext.java:168)
jogamp.opengl.x11.glx.X11GLXContext.makeCurrentImpl(X11GLXContext.java:421)
jogamp.opengl.GLContextImpl.makeCurrentWithinLock(GLContextImpl.java:773)
jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:589)
jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:539)
jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:1263)
jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:1131)
com.jogamp.newt.opengl.GLWindow.display(GLWindow.java:675)

I'm not sure how to debug further to find whereabouts in the C code the problem may lie. I'm open to being educated :)

The device in question is running a modified custom linux OS based on SliTaz 3.16.0
CPU info: Intel(R) Core(TM) i5-2457M CPU @ 1.30GHz

I imagine the issue is related to this system image that we've put together & its compatibility with JOGL.

I'm looking for any info about how I might help identify the incompatibility with further debug - if indeed you think this is the issue.

Thanks :)
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

gouessej
Administrator
Hi

It's not enough, please provide the detailed info log:
http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testing

and try to reproduce your problem on a simple test case.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

Pete
Thanks for the speedy response!

I'll get on that now! - apologies the info was very thin..
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

gouessej
Administrator
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

Pete
This post was updated on .
Tried to run that, but I'm stuck as our image doesn't have javaws as a part of it & I can't install it :(

I can give you some more info however:

Vendor: Intel Open Source Technology Center
Renderer: Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2
Version: 3.0 Mesa 9.1.3
GL Profile: GLProfile[GL2/GL2.hw]
SwapInterval: 1

Requesting a GL2ES2 context.
JOGL v2.3.1
glugen v2.3.1

java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) Server VM (build 25.45-b02, mixed mode)

OS: Linux slitaz 3.16.0 #6 SMP PREEMPT Fri Feb 13 12:00:31 UTC 2015 i686 GNU/Linux

I'm running a new simplistic test app - one that simply calls glClear with a new colour every 33ms - to see if it's simple compatibility or something that is being exacerbated by more complex calls. If the test app breaks overnight I will try get a log.

If you have anything you want me to add to the app to get you more info please let me know,

Thanks :)
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

gouessej
Administrator
Please use JOGL 2.3.2 otherwise any bug report would be invalid. Please use a more recent version of Mesa if possible.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: Application frozen on dispatch_glXMakeContextCurrent0

Pete
I will have to ask the OS guy about Mesa, because the OS build is so slim I can't install or update anything already on it - he will have to update his image.

After seeing if my test app encounters the same issue I will update our main app to 2.3.2 and try that again & get a log from that if it fails.

Thanks for your patience.