Gilson, > Moin
<:-)) >> KRK in his problem got the out of memory problem only >> after repeated additions and deletions from his branch group [...] > That is the ONLY REALLY SURE FACT that is repeated in all good > in-deep-examinations about the frequent-SG-remove/change = mem-leak > = OutOfMemory problem. The j3d-side keeps references to the old > scenegraph and the "native" part of the SG does not get > reclaimed/unloaded. Well, I'd *love* to post a few lines of code that show how I solved it. But I can't, since I don't remember, anymore. Only thing I remember are tedious days of annoying staring into J3D's intestines through the aforementioned refscanner. Wasn't that much fun, really. And a bit of computer voodoo, of course. ;-) > Now we enter the funny world of speculation. There are serval > "theories" about how to get rid of it: > > 1. the "simple" way: > [...] > The theorie said that by adding something to a empty node you would > start a "rebuild" of that node and, in the process, getting rid of > all old references. Is this documented *somewhere*? I wasn't able to find that and I am almost sure that I looked quite hard for a possible solution. > I have not tested it, but up until now it seems to work for him. Yes. Still does. Regards, André =========================================================================== 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".
