We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
IndexSuggestions & BugsSoftware Bugs › Memory Leak in OpenGL / JOGL
Page Index Toggle Pages: 1
Memory Leak in OpenGL / JOGL (Read 587 times)
Memory Leak in OpenGL / JOGL
Mar 5th, 2006, 6:39pm
 
I'm experiencing a memory leak and I think I've narrowed it down to the OpenGL libary or JOGL. Am running processing as classes from Eclipse and got a crash after many hours testing (out of memory) so I've profiled the code (JProfiler) and it's showing a growing number of java.nio.DirectByteBuffer instances. If I don't use OPENGL in the setup() method it goes away (but I need to use OpenGL). have tested with other sketches and I'm failry sure this is where the problem lies. I have an installation going up tomorrow which will be running for a week so it's bound to crash if I don't find a fix quick.. It's a long shot, but if anyone can help ppplease post here asap (or email philworthy@gmail.com))..  will post a bug as soon as I have time.. Thanks a million. -p
Re: Memory Leak in OpenGL / JOGL
Reply #1 - Apr 14th, 2006, 4:02am
 
this bug comes from creating a lot of new image instances inside draw(). see the bug report:
http://dev.processing.org/bugs/show_bug.cgi?id=150
Page Index Toggle Pages: 1