Hmmm...I think it is something like this. Suppose I've a live BranchGroup which is the parent of a subgraph containing possibly other Groups and, in particular, Shape3D's with possibly many Appearances and Geometries. If I detach this BranchGroup then my experience has been that the memory corresponding to that BranchGroup and its subgraph components will not be released *until* you attach and detach another BranchGroup. And, of course, when you detach that second BranchGroup you'll again see a memory leak corresponding to that second BranchGroup.
Now, this may not seem like a big problem since the memory is retained only between successive BG detaches. However, imagine a situation when apart from visualizing the geometry, I'd also be doing other memory allocations as part of a computational steering framework, for example, then it does become a big issue. The dummy attach/detach seem to be an effective workaround for my problem presently. I'm not 100% sure that this leak occurs in general with each and every BranchGroup, or, if it is a function of the various kinds of capabilities such as By_ref, U_C_I_O, etc. The general advice that I have from Chien, hope that I paraphrase him correctly and which may or may not be a fix for this particular problem, is to perform all BG detaches (and probably attaches too) from within a behavior especially if the attaches and detaches are very !!!rapid!!!. Vaidya >On Wed, 14 Apr 2004 13:41:22 +0200, M. Pfeiffer <[EMAIL PROTECTED]> wrote: >To make that clear: > >the method you described helps to free memory at the detached >BranchGroups formely parent? > >N. Vaidya schrieb: >> When a BranchGroup is detached, Java 3D will not let go >> of the memory >> retained by that BranchGroup. The workaround, and a >> pretty dumb one at that, >> I've devised is to simply attach and detach a dummy >> BranchGroup to flush >> out the retained memory. And this has been acknowledged >> by Kelvin Chung as >> an effective workaround. IIRC the BugId for this is >> 4884065. >> Clearly one of the most annoying bugs that need to fixed >> when Java 3D goes >> public. >> >> Chien may have probably more to tell you on this subject >> since I've >> *bugged* (no pun intended) him quite a bit about that >> recently :-). >> >> Vaidya >> >> > ========================================================================== >> 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". >> >-- >Virtual Worlds Productions >Software Development Group >http://www.VirtualWorlds.de > > ========================================================================== >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". =========================================================================== 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".
