Thanks for the response!!! I read it very carefully.
I don't think it's a memory issue for several reasons. 1. I use -Xmx1024mb and so there's plenty of memory. 2. If I take out the setCoordinte code, there are no delays. 3. If I detach the group, update it and then reattach, there are no delays, either! (but lot's of blinking!!!)
(BTW, I'll address this in another email soon... but if I keep the update code, my program does run out of memory eventually (although there are no new classes being created!!!!))
What else can it be? As a reminder, I have this code:
for (int i = 0; i < height;i++)
for (int j = 0; j < width; j++)
myTA.setCoordinate(i*width+ j, mySurface.pGet(i, j));
Many thanks!!!!
trz <[EMAIL PROTECTED]> wrote:
Bura Tino wrote:
> My I follow up my own message. The problem was that the same command
> that updates the location of a surface often takes an unreasonably long
> time. Here's the code snipet:
>
Hi,
it could be the garbage collector. Try to run the prog with -verbose:gc
to verify it.
If it's so, you have to look where you create new objects (maybe every
frame) and find a way to avoid this (reusing object or the like). And
you can try to give jvm more memory with -Xms32m -Xmx64m.
Bye
===========================================================================
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".
Do you Yahoo!?< br> Yahoo! Mail Plus - Powerful. Affordable. Sign up now
