[circle] Memory leak (was Roadmap for 1.0 ??)

[Thomas Mangin]

> |Yeah, I've come accross memory "leaks" in python before. I never did
track
> |them all down. :(
> The leak isin the way object are created and not destroyed as the garbage
> collector can not notice they are not in use anymore, I do not know any
> better myself.

|Only way I know of that garbage collection can fail, is if a circular
|reference occurs...

|Is there another way?

I am not an expert but here are a few links ..

Document about memory ...

http://www.python.org/doc/current/ext/refcounts.html
http://www.memorymanagement.org/articles/begin.html

Possible explaination:

Circular reference as in
http://www.pythonware.com/products/xmlrpc/bug-xmlrpc1.htm
http://lists.fourthought.com/pipermail/4suite-dev/2003-March/001253.html

Libraries leak
http://sourceforge.net/tracker/index.php?func=detail&aid=559117&group_id=547
0&atid=105470
http://www.daa.com.au/pipermail/pygtk/2003-March/004798.html

C code missing DECREF as in C code
http://mail.python.org/pipermail/python-bugs-list/2001-September/006959.html

OS issues as in
http://lists.spread.org/pipermail/spread-users/2002-October/001152.html
http://lists.spread.org/pipermail/spread-users/2002-October/001154.html


Any solutions ??

Memory profilers
http://sourceforge.net/tracker/index.php?func=detail&aid=401229&group_id=547
0&atid=305470

Memory leak detectors
http://www.python.org/ftp/python/contrib-09-Dec-1999/System/Cyclops.README
http://www.python.org/ftp/python/contrib-09-Dec-1999/System/Cyclops.py.Z