> Tim Bray wrote:
> >
> > I'm modeling an (effectively) infinitely large surface by cleverly
> > stitching things into the scene graph ahead of them and whipping them
> > out behind as the user moves around. Works OK, except the memory
> > usage seems to grow monotonically until after a couple minutes java
> > barfs on out-of-memory.
>
> This has been a well documented bug with Java3D in its shape nodes.
> Basically what seems to be happening is that the Shape3D objects and/or
> their geometry (nobody seems to have really worked out exaclty what is
> leaking AFAIK) are not being GCd internally. I can't remember the exact
> reason off the top of my head but I seem to recall that it is something
> on the native side of the code not releasing their memory.
>
> Unfortunately, there is no real solution to this.
The only way to solve these kinds of problems is having access to
the sourcecode... only way to scratch the itch, so to speak.
Isn't J3D supposed to be SCSL'ed?
/Mats
===========================================================================
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".
