Hello Mark, I have carefully looked at the bug 4794994 and I do believe that it is not related. At least not with the explanation given for that bug.
I have prepared for you a test case to look at the problem. My case is related to sharing "geometries", i.e. TriangleStripArrays. Whenever I have the same TriangleStripArray used by more than 1 Shape3D, memory leaks start appearing. What strikes me is that gc works when using different geometries and stalls when sharing geometries. If it were for the explanation of bug 4794994, it shouldn't work in both cases. When running the program, it will use a shared TriangleStripArray. You will see a steady increase of the memory usage until you finally get an OutOfMemoryError. If you change the class variable "shareGeometry" to false it will create a new TriangleStripArray for each shape. The memory usage does not increase and remains low. The only difference for those cases is the way the shape3d is created (line 104). The scene graph consists of 1 BG + 100 TG, each containing 1 SH with 1 TriangleStripArray of 1 triangle (3 vertices). Bug was tested on w2k, jdk 1.4.1 + jdk 1.4.1_02, j3d 1.3 fcs. Kind Regards, Florin -----Urspr�ngliche Nachricht----- Von: Mark Hood [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. M�rz 2003 00:16 An: [EMAIL PROTECTED] Betreff: Re: [JAVA3D] WG: [JAVA3D] ? Garbage Collection - memory does not decrease ? > Date: Mon, 10 Mar 2003 16:51:20 +0100 > From: Florin Herinean <[EMAIL PROTECTED]> > > So, I'm asking again, since there was no answer before, what's happening > when a scenegraph is made live that shared geometries are not released for > garbage collection ? Is it a bug or am I doing something wrong ? If you're using SharedGroup, then the following bug in Java 3D 1.3.1 beta1 is apropos: bug 4794994 - "Memory leak when SharedGroup removed" This bug is fixed in the upcoming Java 3D 1.3.1 release. -- Mark Hood
SharedGeometryBugTest.java
Description: Binary data
