Isaac,
I'd guess that the memory hog is buried in the not shown method
makeOneGraph().
That's where I would start digging if Mona's suggestion about upping the
memory you give to the JVM at startup does'nt cut it.
All the code you have shown us, does not seem to be relevant for the problem
to occur.
But the code you showed bothers me somewhat: why are you making things so
incredibly complicated?
- a loop with a switch inside (same point as Brandon was making earlier)
which just amounts to processing things in sequence; the 40something lines
the loop makes up can be done in just 6 lines - one for each of the 6 cases
( unless you are paid by #lines produced and really need to crank up your
linecount with hacks like that)
- consider this code snippet : ...
Vector comp1 = new Vector();
comp1= processComplement(hix,viis);
objRoot.addChild(makeOneGraph(k,comp1));
You are making a new Vactor instance and throwing it away on the spot!
Are you sure you know Java? Are you sure you want to tackle Java3D?
H.
===========================================================================
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".
