Posted by
Sven Gothel on
Oct 24, 2011; 1:07pm
URL: https://forum.jogamp.org/JOGL-current-application-consumes-more-and-more-memory-tp3448015p3448049.html
On Monday, October 24, 2011 02:56:05 PM seb [via jogamp] wrote:
>
> Hello Jogl list,
>
> we are currently writing a JAVA/JoGL application using the following JOGL
> version:
>
>
http://jogamp.org/deployment/jogamp-current/jogl-all-awt.jnlp to deploy
>
> the application starts fine but after a while the process starts eating-up
> memory up to 2Gbytes (we are estimating the application should consume in
> the order of 200MBytes total)
>
> We have tried to use the classic JAVA tools to profile memory usage but they
> do not report memory objects explaining 2GB of RAM.
>
> The problem is present on very different setups (linux 64 + nvidia, windows
> 64bits + basic sandybridge laptop....). How can we debug memory allocations
> in the JNI side ? Any other suggestion appreciated.
>
Thank you for your post + findings so far.
Please validate against:
http://jogamp.org/deployment/archive/master/gluegen_424-joal_228-jogl_526-jocl_455/archive/I have profiled NEWT apps on desktop and mobile/Android and cannot confirm
a heap leak in our current codebase. On the contrary, I was able to reduce
a few leaks while working on the Android port.
Since we cannot talk about a phenomenom we don't experience,
it would be best if your can provide a most small test application,
best a unit test, to us.
Then we are able to help profiling and finding the culprit.
Another very essential information is to know the exact platform[s]
on which you are experiencing this heap utilizations.
Please follow the FAQ 'Bugreports & Testing' thoroughly
http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_TestingWhat would be nice to have is:
http://jogamp.org/wiki/index.php/Jogl_FAQ#Runtime_Version_Check~Sven