[pygtk] memory leak !?

[Tony Nelson]

At 10:50 PM +0200 6/13/06, Adrian Immler wrote:
>NZ> Adrian,
>NZ>
>NZ>     I have had a similar problem in the past. I did some research into
>NZ> it and found out you need to garbage collect manually after you no
>NZ> longer have references to the image. I don't remember why I did this,
>NZ> but I have something like this in my code:
>NZ>
>NZ> import gc
>NZ> gc.enable()
>NZ> ...
>NZ> set_image(someimage):
>NZ>     # set the image
>NZ>     gc.collect()
>NZ>
>NZ> I hope this helps you.
>NZ>
>NZ> Natan
>
>
>indeed this works and solved the problem. but it think that the root of
>the problem still remains and is some kind of bug probably in pygtk.

It would have to be a circular reference (with a __del__() method?).  (I've
never done this, but) you can get a list of that sort of thing using the gc
module.
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson at georgeanelson.com>
      '                              <http://www.georgeanelson.com/>