More information: It appears that this NOT a problem under the DirectX version
of Java3D.
-----Original Message-----
From: McCall, Jonathon D
Sent: Wednesday, November 29, 2000 9:28 AM
To: [EMAIL PROTECTED]
Subject: Memory Leak?
I'm hoping someone can shed some light on my problem.
Because of memory problems with Java and swing components, we have
implemented window reuse in our application. In this way we reuse our windows
and avoid the continuous leaking that was taking place with swing components not
being garbage collected on all VMs.
Now for my problem. I've got a window that creates a Java3D canvas. I
can reuse this window dozens of times in my application. While reusing this
window I call Runtime.totalMemory() and Runtime.freeMemory(). These numbers
appear to remain fairly constant, with the difference between the total and free
being about 8 meg used. So far so good.
When I observe the Windows Task Manager memory usage for my application,
the JavaVm grows with each reuse of my window by about 4 meg! This memory is
never returned to the system, however, as noted above, the Runtime thinks it
has. Calling runtime.gc has no affect.
I running on Windows 2000, using the Java 3DTM 1.2.1 Beta 1 release,
however, this problems appears under older release versions of Java3D also.
Any ideas would be appreciated.
Thanks,
Jon McCall
Battelle
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
