Posted by Xerxes Rånby on Jul 29, 2016; 11:44am
URL: https://forum.jogamp.org/JVM-Crash-with-SIGSEGV-tp4036967p4037003.html

gouessej wrote

I understand your position, it's more professional. I'll let you know if I can clarify something.

Edit.: Calling some OpenGL or X11 methods not from the right thread / process is usually a bad idea, especially when the native memory of some structures has already been released.

It is highly likely that the crash huy1912 experience is caused by not calling AWT + Swing methods from the event dispatch thread.

When we tested the 2.1.3 release we did run into a similar looking crash in glXChooseVisual alternatively in glXCreateNewContext when the AWT removeNotify was called from a non AWT-EDT thread by the IcedTea-web browser plugin.
https://jogamp.org/bugzilla/show_bug.cgi?id=910
https://gist.github.com/xranby/3e3b4ebd5b1fd67cef13 - sigsegv [libGL.so.1+0x6bf82] glXChooseVisual+0x6472 during GraphTextDemo applet window close on 32bit ubuntu 12.04 + icedtea-web using opengl 4.3 core profile 4.3.0 NVIDIA 319.32 drivers

To be sure huy1912 exerience a issue then we need to see your full hotspot error log.
Please provide all information stated in: https://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testing

If we have a testcase and a full bugreport then we can investigate if a similar workaround that we added to NewtCanvasAWT may be added to GLCanvas to prevent the crash even if removeNotify was called from the wrong thread.