Hi,
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>X-Priority: 3 (Normal)
>X-MSMail-Priority: Normal
>Importance: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
>Date: Wed, 26 Apr 2000 01:16:09 -0400
>From: Dean Keeler <[EMAIL PROTECTED]>
>Subject: [JAVA3D] memory leaks when using java3d in an applet
>To: [EMAIL PROTECTED]
>
>Hi,
>
>I have written an applet that uses Java3d and loads in a vrml file. I have
>noticed that when I leave the page containing the applet memory does not
>appear to be freeing up automatically. It seems that each time I reload the
>applet, it takes up more memory, runs slower, and will eventually max out
>the available memory and hang the system or crash the system.
>
>Is there something else I have to do to clean up objects when using Java3D
>or is this taken care of by the garbage collector? Within the applet I have
>classes that contain threads that are running. In these classes I have
>written a finalize routine that basically causes the thread to go into a
>wait state and then I set the thread variable to null. Can someone give
>some suggestions as to how I can free up memory better when the applet is no
>longer being used? I would very much appreciate it.
>
To cleanup threads associated with Java3D v1.2, it is necessary to
either
(i) For each View, remove all canvas3D from it and make sure
the ViewPlatform associate with it not live.
In the later case, either detach the viewPlatform branch
or use view.attachViewPlatform(null).
OR (simply)
(ii) Detach all branch groups under the VirtualUniverse.
There are also some memory leak bugs in v1.2beta2 which
is fixed in the upcoming FCS release.
Thanks.
- Kelvin
------------
Java 3D Team
Sun Microsystems Inc.
===========================================================================
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".
