Posted by InteractiveMesh on Dec 17, 2013; 2:21pm
URL: https://forum.jogamp.org/java3d-memory-leak-with-threads-tp4030899p4030936.html

Beside the five Java 3D core threads another 9 threads will be created for each McIDAS-V view-tab because each one includes a VirtualUniverse, View, and Canvas3D instance.

In case of 10 view-tabs the JConsole monitor reports 124 threads in total and a non-/heap memory usage of 300 MB (without any loaded data).  

As of my experiences with other Java 3D multi-view applications such a number of threads and its memory consumption don't cause real problems.

While running McIDAS-V the core threads and only the threads of the visible view-tab are running on demand, all other are waiting.

I can't provide any feedback concerning the influence of the python script.

August