Dear fellows, we are working with highly complex structured hierarchical objects in bioinformatics and do allocate a hugh amount of memory (>1000 MByte).
As soon as the depth of the object tree becomes too high, JAVA is no more able to remove unreachable temporary objects, leading to more and more uncleared memory and at last to "OutOfMemory". The problem might arise from used big loops out of one routine, since I read some weeks ago that the garbage collection can only remove temporary objects when the calling master method is terminated. (I think these references are called "weak", "phantom" or whatever). Does anyone know, how I can enforce memory to be freed whenever a reference becomes unreachable, meaning that these temporary objects become reachable for the garbage collection even if the calling method has not terminated? It would help us a lot to find a workaround, because this property seems to be a severe limitation in nerdy bioscience applications! This request does not really match the JAVA2D homepage, although we also do a lot of graphical animation. But the error certainly is not from JAVA2D, so perhaps somebody also knows a more appropriate mailing list or resorce to discuss my problem? Thank you all, Sven ________________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
