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 <[EMAIL PROTECTED]>:
> Python 2.5.1
> GTK: (2, 12, 0)
>  pyGTK: (2, 12, 0)
>
> Sorry I forgot to mention the versions.
>
> David
>
>
> 2007/9/27, Pádraig Brady <[EMAIL PROTECTED]>:
> > 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
> >
> >
>

Attachment: demo_v5.py
Description: Binary data

Attachment: element.glade
Description: Binary data

Attachment: fenetre.glade
Description: Binary data

_______________________________________________
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to