Posted by huy1912 on Aug 01, 2016; 3:45am
URL: https://forum.jogamp.org/JVM-Crash-with-SIGSEGV-tp4036967p4037009.html

Xerxes Rånby wrote

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

As mentioned in the original post, the system using its own animator thread to draw on each GLCanvas (-Djogl.1thread=false) instead of heavily relying on the EDT thread for drawing. The EDT thread is used to manage the UI events as well as provide the drawing data to each GLCanvas if UI update needs to be redrawn.

Xerxes Rånby wrote

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

JOGL, Platform and OpenGL Version: see test.log
Hotspot error log: see hs_err_pid3137.zip.

Xerxes Rånby wrote

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.

GLCanvas.removeNotify explicitly mentions that User shall not call this method outside of EDT, read the AWT/Swing specs about this. So this method is not invoked outside of EDT in my system.