[pygtk] Need help to find origin of a mem leakage

[David Tremouilles]

Here is an updated and cleaner version of the leaking code.
I do not understand "who" is keeping a reference to the "contents" of
each on tabs after removing it.

David

2007/9/27, David Tremouilles <david.trem at gmail.com>:
> Python 2.5.1
> GTK: (2, 12, 0)
>  pyGTK: (2, 12, 0)
>
> Sorry I forgot to mention the versions.
>
> David
>
>
> 2007/9/27, P=E1draig Brady <P at draigbrady.com>:
> > David Tremouilles wrote:
> > > Sorry forgot the attachments
> > >
> > > Hello,
> > >
> > >  I'm struggling with a memory leakage of my pygtk app for quite some
> > > time. Could somebody help me?
> > >
> > > Seems this is not a cycle reference (checked with gc.garbage) but I'm
> > > definitely not an expert...
> >
> > What version of python are you using?
> > http://evanjones.ca/python-memory-part3.html
> >
> >
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: demo_v5.py
Type: application/octet-stream
Size: 2958 bytes
Desc: not available
Url : http://www.daa.com.au/pipermail/pygtk/attachments/20070927/bb1984ab/d=
emo_v5.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: element.glade
Type: application/octet-stream
Size: 1811 bytes
Desc: not available
Url : http://www.daa.com.au/pipermail/pygtk/attachments/20070927/bb1984ab/e=
lement.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fenetre.glade
Type: application/octet-stream
Size: 1955 bytes
Desc: not available
Url : http://www.daa.com.au/pipermail/pygtk/attachments/20070927/bb1984ab/f=
enetre.obj