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

[hendrich at informatik dot uni-hamburg dot de]

------- Comment #6 from hendrich at informatik dot uni-hamburg dot de  
2006-06-07 14:05 -------
> How many images, what kind of images, how big are they?

For my tests yesterday I tried a directory with a few hundred medium-sized
JPGs (roughly 800x1200 each).  However, there are also a handful of large black
and white scans (2400x3600 1bit PNGs) in the directory. I am pretty certain
that yesterdays crash happened at the point where the slideshow has to read
those larger images.

I tried today on a directory full of 6MPixel digicam JPEGs, and niffler
survived for about 50..100 images. However, memory usage as reported by top
quickly reached about 300M Virt and 300 RSS in steady state, and up to 600M
Virt 450M RSS when loading a new image. I stopped the test at that point.



> Do you generate thumbnails?

No.


> After how many images in the slideshow does the program become unusable?
> Does the same thing happen if you just choose next by hand?
> And how exactly do you start jamvm, any other arguments besides -Xmx300M?

Crashed after about 100 images; seemed responsive enough before that (but most
images were rather small on yesterdays test).

/opt/jamvm/bin/jamvm -Xmx300m -Xms100m


-- 


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