I forgot to add that the memory leak that I mentioned happens usually with textured objects. It is possible that these are the ones in my app. which have such high memory footprint to be conspicuously evident as a leak.
Raj >On Wed, 25 Jun 2003 16:32:43 -0600, N. Vaidya <[EMAIL PROTECTED]> wrote: >>On Wed, 25 Jun 2003 15:06:27 -0700, Kelvin Chung <[EMAIL PROTECTED]> >wrote: > >> >>Bug 4884065 - Memory leak in SetLiveState when branchGroup remove >> >>is filed for this. >> >>Actually this is not that serious as the memory will free next time >>the same SimpleUniverse is used. Otherwise you can always set >>SimpleUniverse to null to force cleanup. >> > >Just want to make sure that I understand the magnitude of this leak. >If I make live BranchGroups A, B, C and detach BG C, then there is >a memory leak corresponding to BG C, i.e., the very last BG that is >detached ? And this memory leak will get flushed out if I make live >a new BG D ? > >Well, my app. has been exibiting a memory leak such as the one above >thru' at least the last 2 versions. And the workaround that I've been >using is to make live a small memory object to flush out a large object. > > >Thanks > >Raj > > ========================================================================== >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".
