memory leaks in 1.5.2 Python interpreter

Aahz Maruch aahz at panix.com
Fri Jan 25 04:17:39 CET 2002


In article <3de7ef11.0201241906.3c277020 at posting.google.com>,
Michael McCarthy <michael at tcsi.com> wrote:
>We have observed memory leaks in the 1.5.2 Python interpreter under
>Purify.
>
>If we check for new leaks immediately before and immediately after
>invoking PyEval_CallObject, we often see a leak originating in
>PyTuple_New as invoked by eval_code2.
>
>Can anyone tell me whether or not later versions of Python have
>addressed any memory management problems? We would like to know if
>moving to a newer version will clear up any memory leaks.

Some problems have been addressed.  The current most stable release is
Python 2.1.2; you might try that.
-- 
                      --- Aahz  <*>  (Copyright 2002 by aahz at pobox.com)

Hugs and backrubs -- I break Rule 6                 http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista   

"I support family values -- Addams family values" --www.nancybuttons.com



More information about the Python-list mailing list