Bug 160 - Resource leaks in GLJPanel
Summary: Resource leaks in GLJPanel
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 1
Hardware: All all
: P3 normal
Assignee: Sven Gothel
Depends on:
Reported: 2005-05-01 11:01 CEST by Sven Gothel
Modified: 2010-03-24 07:47 CET (History)
0 users

See Also:
SCM Refs:
Workaround: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2010-03-24 07:47:48 CET

---- Reported by kbr 2005-05-01 23:01:29 ----

There are some known resource leaks in the GLJPanel. The hardware-accelerated
path does not clean up the associated pbuffer or toplevel window and the
software rendering path does not clean up the associated offscreen context.
These should be fixed by overriding addNotify / removeNotify as in the GLCanvas.

See also the following thread:

---- Additional Comments From kbr 2005-05-01 23:06:28 ----

Added addNotify and removeNotify to GLJPanel which clean up the
associated OpenGL contexts and other resources. Extended JRefract demo
to stress GLJPanel creation and destruction. New code appears to be
correct. Can see resource leaks when the bunny is loaded over and
over, but believe these are probably due to allocation of large NIO
buffers that are not getting finalized promptly. Stressing the Gears
demo with both the pbuffer and software rendering paths shows that the
OpenGL resources are being reclaimed properly.

--- Bug imported by sgothel@jausoft.com 2010-03-24 07:47 EDT  ---

This bug was previously known as _bug_ 160 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=160