I’m currently coding a new program, which opens a lot of large images
(photos) with Gdk::Pixbuf. These are “freed up” correctly (no more
alive reference to the object in my program), but the ruby program is
never freeing memory to the OS, unless I explicitely trigger the GC.
This is a big problem as the computer crawls swapping after a little
I am wondering whether there should be some kind of GC “hints” from
rg2 (I have zero knowledge of ruby GC internal)? The following quick
test shows that repeatedly allocating and reassigning with Array.new
grows memory up until a “reasonable” amount, whereas Gdk::Pixbuf.new
Used image is http://zarb.org/~gc/t/pa.jpg
(using ruby 1.8.6, rg2 0.16.0, gdk pixbuf 2.10.12)
Guillaume C. - http://zarb.org/~gc/
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.