Posted by Ivan on Dec 05, 2016; 11:07am
URL: https://forum.jogamp.org/GLContextShareSet-leaks-GLContexts-tp4037493p4037498.html

Ok thanks, fyi here is the full context:

Our users use virtualized workstations, so each physical workstation is shared by many users.
The actual problem we encountered is that, after a while, the XServer returns an error when we try to create a new context.
Running the following command:
/usr/sbin/lsof -U | grep socket | grep java | wc -l

Has shown that everytime we open and close a window using a GL context the XSocket is not closed/released (value returned by the command above is increasing).
For some reasons it happens only on those virtual workstation, on a real one, the socket is actually closed.
Our assumption/hypothesis is that a proper local XServer is more aggressive and release the resources/native-context even if it's still referenced by the java application.

As many users use the same XServer, the limit is "quickly" reached.