Yes, please enter a bug for this memory leak. I also experience it using: pygtk 1.99.17 gdk-pixbuf 0.22.0
In my program, I experience memory growth like this: using gtk.gdk.pixbuf_new_from_file, then scale_simple: after loading first image: Total:147MB, RSS:17.7MB, Shared:7.2MB after loading fifty-sixth image: Total:276MB, RSS:146MB, Shared: 7.3MB but if I use PIL.Image.open and img.resize: after loading first image: Total:145MB, RSS:16.4MB, Shared:7.2MB after loading fifty-sixth image: Total:146MB, RSS:16.4MB, Shared: 7.2MB Total memory usage will flucuate up to ~158MB, depending on the size of the image that is loaded, but will always drop back to the original memory usage. I can send my program to anyone who requests it, but you will need pygtkglext and PyOpenGL installed to run it. -D ____________________ * From: u+pygtk * Subject: [pygtk] Memory leak with gdk-pixbuf * Date: Sat, 28 Jun 2003 13:29:28 -0700 In November 2002 on this list, John Fremlin reported that the pixbuf object returned by gtk.gdk.pixbuf_new_from_file() do not seem to be garbage collected. He provided example code that can be seen at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg04867.html I also noticed this using Debian packages of Python 2.2, gdk-pixbuf-0.22.0 and PyGTK 1.99.16. Is it a known problem? Shall I file a bug report at Bugzilla? /Ulrik __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
