> Clemens, you were right... I am ashamed. I thought I > was cleaning > that reference, while I was actually not. I guess I > over-sought this > possibility simply because everything was working > fine with OSXImage > or awt.ToolkitImage (even though the reference was > not cleaned up). > > Thanks a lot and my apologies for the trouble,
No problem at all, however I can really recommend using those tools: - jconsole: To moonitor jvm behaviour (gc-workload, ...., generate heap snapshots) - jhat: To inspect heap-snapshots (can be very helpful to find leaks and other memory hungry stuff) - Netbeans profiler: Run it every now and then and see whats going on. It even helped me often to find hidden bugs where my code hit a slow-path even for very common operations just because I forgot to write a fast-path ^^ lg Clemens [Message sent by forum member 'linuxhippy' (linuxhippy)] http://forums.java.net/jive/thread.jspa?messageID=246742 =========================================================================== 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".
