Andrew,
Try Java3D 1.2.1 beta 2 - it appears much more reliable on memory usage.
(or wait for 1.2.1 final release which as Sun has stated should be
"soon").
We found going to JDK 1.3 helped "mask" the memory loss with the
incremental garbage collection. JDK 1.3 is a nice improvement but it
won't cure your problems.
- John Wright
Starfire Research
Andrew Phelps wrote:
>
> We are experiencing a memory leak with the following set up:
>
> Solaris 7
> Sun x server
> Java3d 1.2
> JDK1.2.2
>
> Our code is performing off screen rendering of 3D scenes and sending the
> images back to a thin client. We have tested this on 3 platforms:
> Linux : there is a fault with the blackdown J3D texture mapping
> NT: successful
> Solaris: appears to have a memory leak, OR X fails
>
> We are keen to use a Sun box but we are experiencing two problems. Firstly
> X (inconsistently) fails and requires a restart. We have not been able to
> track why this is happening. Secondly: if X remains up we then see no
> release of memory (X process) after each 3d render. i.e. the memory rapidly
> increases until X fails.
>
> Has anyone experienced similar problems? Any suggestions?
>
> Any comments appretiated,
>
> Andy Phelps
> DiyPrint.com
> Technical Architect
>
> ===========================================================================
> 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".
