[Bug awt/27917] Massive memory leak in Graphics2D image operations

[hendrich at informatik dot uni-hamburg dot de]

------- Comment #3 from hendrich at informatik dot uni-hamburg dot de  
2006-06-06 18:18 -------
Hello Mark, 
with your patch in, garbage-collection seems to (partially) work for images
again. I tried running the niffler slide-show at the default speed for about 40
images, and 'top' reported about 300M Virt and 200M RSS, periodically reduced
to roughly 150M Virt after garbage-collection. Much better than without your
patch! 

I then reduced the slide-show interval to about 0.5 seconds, which makes jamvm
load the images about as fast as it can. Memory size quickly reached about
700+M Virt and 500M RSS, at which point my Linux crashed. This is only the
second kernel crash that I remember (and the kernel has now equaled WinXP in
this regard, too, after 3+ years of daily usage. Perhaps I should really
upgrade the main memory, after all :-)).

Note that I specified a -mx300M flag to jamvm, so that jamvm shouldn't have
allocated more than 300MByte in the first place. Is the Gtk/Cairo memory
allocated differently from the Java heap?!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27917