OK, I’ll try sometime (I’ve only been running the JWS demos so far, and I’m too busy right now to sit down for more than about 1 minute!)
I’ll have a go with 1.5beta as well, see if the same thing happens.
I sincerily believe the only right solution is to get rid of these excessive object creations. I’m sure JOGL, LWJGL or jME (scenegraph also) do not act like this.
Sure you can set your -Xms -Xmx into 1gigabyte and “buy” big timewindow before first gc bang occurs, or use -incgc and tweak your garbage collector to run all the time on the background, but the overall performance suffers from this. I haven’t done benchmarks but I believe fps takes a noticeable hit because of this. I am now talking about scenes that have hundreds of objects moving.
Again, the “guilty” part is TransformGroup.setTransform() call. It does several functions and trashes memory bigtime.
I am positive that it happens, or at least in the expense of performance. Nothing changes the facts that there’s lots of work for GC to do in any case.
Last words and reasons why I started this thread:
Ok, perhaps we should remember that Xith is heavily under development and just accept the facts, I’m sure this will be corrected before v1.0 is out, I just wanted to prioritize this issue a bit more on the development queue 
Cheers, Jani!
OK, I will try to take a deeper look at setTransform(…) nearest week. This can be non-trivial task, because of transform shader and state management is involved… but we will see.
Yuri
Hi,
Now setTransform(…) on TransformGroup should produce no garbage. Please test if your apps run OK with current CVS version.
Yuri