I'm almost certain that the JVM will garbage-collect *all* objects which are no longer referenced. You should definitely download a memory profiler like JFluid (part of NetBeans 4.0) or YourKit Profiler, to find out where your memory leak is.
-Keith
Sven Mielordt wrote:
Unfortunately, this induced my present memory problems: When being deep inside inner classes, TEMPORARY objects are NOT GC'd. (Tree branches can be cut off, this is not the problem.) For me this is a bug in JAVA since I do not get the point why this must be. Probably I will have to unravel this structure into independent classes, but this is a hard way and not as performant as before.
Does anyone know a way how to enforce TEMPORARY objects of inner classes to be GC'd ???? This might also be the reason why DOM and SAX parsers make problems as well on VERY BIG XML documents.
=========================================================================== 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".
