[Python-Dev] update on memory leaks in 2.2 (original) (raw)

Guido van Rossum guido@python.org
Fri, 07 Dec 2001 11:38:35 -0500

Command line: (longexp crashes purify for some reason) ./python -E -tt ./Lib/test/regrtest.py -u network -x testlongexp.py

Results: 168 tests OK. 1 test failed: testsocketssl 15 tests skipped: testal testbsddb testcd testcl testcurses testdl testgl testimgfile testlinuxaudiodev testnis testntpath testopenpty testsundry testwinreg testwinsound

A few of these skips weren't expected: test_sundry, test_openpty, test_bsddb. What's missing to run those?

test testsocketssl crashed -- socket.sslerror: SSLCTXnew error

Works for me. Probably your platform. The SSL code sucks anyway.

When running testcurses:

test testcurses crashed -- curses.error: cursset() returned ERR

Works for me.

Uninitialized Memory Reads (don't think these are python's fault): gdbmopen() gdbmmodule.c:68 getaddrinfo() socketmodule.c:636 Memory Leaks: NONE

Woohoo! So I'll close the remaining leak report!

Potential Memory Leaks:

1012 from 4 different allocating points -- all in WeakRef

Any more info on these, or are these just red herrings?

Things look great!

Agreed.

Let me know if any of the skipped tests ought to have been run. Most likely possibility seems to be bsddb, sundry also needs bsddb.

Ah, that's why sundry fails. I think it shouldn't depend on bsddb; I'll look into that.

--Guido van Rossum (home page: http://www.python.org/~guido/)