Running 128M now.  What happens if you specifiy 128 or 256 and the user only has 64MB?   I assume virtual memory kicks in then, and potentially a lot of hard disc thrashing?
 
Scott
----- Original Message -----
Sent: Sunday, May 05, 2002 2:12 PM
Subject: Re: [JAVA3D] wierd java.lang errors

Seems like a normal out of memory error.
 
Try to increase the available heap size (example: "java -mx256M -ms64M myapp.MyApp" for 64MB initially and 256MB before OutOfMemoryError).
 
Good luck!
 
Regards,
Fredrik
 
----- Original Message -----
From: Scott
Sent: Sunday, May 05, 2002 7:39 PM
Subject: [JAVA3D] wierd java.lang errors

Anyone seen this before?   It happens very intermittently, I can't seem to reproduce it.  I'm using 1.3 beta 2, D3D flavor.
 
Funny thing is, at this point anyway, I'm not using any SharedGroup objects, but that's where the error came from... (unless the scenegraph compile uses SharedGroups?)
 
Scott
 
java.lang.OutOfMemoryError
        <<no stack trace available>>
java.lang.ArrayIndexOutOfBoundsException
        at javax.media.j3d.SharedGroupRetained.updateChildLocalToVworld(SharedGr
oupRetained.java:533)
        at javax.media.j3d.TransformGroupRetained.updateChildLocalToVworld(Trans
formGroupRetained.java:972)
        at javax.media.j3d.TransformGroupRetained.processChildLocalToVworld(Tran
sformGroupRetained.java:819)
        at javax.media.j3d.TransformStructure.processCurrentLocalToVworld(Transf
ormStructure.java:306)
        at javax.media.j3d.TransformStructure.processMessages(TransformStructure
.java:186)
        at javax.media.j3d.StructureUpdateThread.doWork(StructureUpdateThread.ja
va:83)
        at javax.media.j3d.J3dThread.run(J3dThread.java:250)

Reply via email to