[pygtk] Memory leak with gdk-pixbuf

2003-08-22 Thread David Braaten
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

[pygtk] Memory leak with gdk-pixbuf

2003-06-28 Thread u+pygtk
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 pac

[pygtk] Memory leak with gdk-pixbuf and pygtk-1.99.13

2002-11-26 Thread John Fremlin
The following program eats all memory because GDK pixbufs do not seem to be garbage collected. I have Python 2.2 and gdk-pixbuf-0.20.0 How is it that you get away with having NULL tp_dealloc destructors on the wrapped types? Surely that needs to be changed to typename_unref on all types? impor