I just built cacao-0.97 with current classpath cvs in order to track down a memory leak in my image-viewer application . When running a slideshow, the JDKs (1.4.x, 1.5.x, 1.6.x) work fine, but jamvm+classpath slowly leak memory until the JVM crashes. See gcc bugzilla #29420 for details. This occurs after about 200..400 images, depending on -Xmx memory limit and image size. All of this on Linux x86. Unfortunately, it seems that cacao leaks even more memory than jamvm, on the order of 20+ MBytes per image. It seems that image data is not collected at all, and a slideshow will crash after just a few images. No small testcase yet, but you can download the binaries and sources of Niffler from : cacao -Xmx300m niffler.Niffler menu -> select directory -> <select a directory with GIF/JPEG images> menu -> slideshow -> start slideshow (linear) ... crash Note that this happens also when thumbnails-generation, histogram, and exif-preview are switched off: just the plain image loading and image rendering. Could someone please confirm that image/JNI memory is not collected at all by cacao? If so, I don't need to bother testing again... Anyway, I have set this to "critical" for now.  http://tams-www.informatik.uni-hamburg.de/people/alumni/hendrich/niffler/
Confirmed. The bug seems fixed in jamvm 1.4.4 and classpath cvs (but I can reproduce a small leak with jamvm 1.4.2 and a major leak with cacao 0.97).
Here is the GNU Classpath PR: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29420
I have fixed a memory leak in the Boehm-GC. Could you try again and report what the current memory usage is?
I seem to have hit the same bug using http://www.statsvn.org/. Just run it on any large-ish svn repo (cacao for example), and it will OutOfMemoryError pretty soon.
Still reproducible with current cacao and classpath, although the bug mentioned in comment #3 is supposed to have been fixed years ago. Further, it's unbelievably slow. Not reproducible with OpenJDK.
Comment #1 by email@example.com on 2006-11-09 21:18:37