I have read the Users Guide and searched the mailing list, but haven’t found an answer to the following question:
When you are done with a JOGL canvas, how do you insure that all of the underlying operating system/OpenGL resources have been disposed of?
With my application, it is expected that GLCanvases will be created and destroyed over time as the users sees fit. However, I am finding that system resources are not being released even after the windows containing these canvases have been closed. Based on the symptoms, it looks like the hardware accelerator memory is being exhausted…
Is there an explicit “destroy” method that would perform this job? So far, I haven’t found one in the public API.
If not, then what is the likelyhood of something like this being implemented?