[PEAK] Memleak in PEAK with Python 2.3.5 with ldap-module installed ?
Ulrich Eck
ueck at net-labs.de
Tue Apr 12 13:40:02 EDT 2005
Hi Phillip,
i just upgraded to the latest cvs of PEAK and rerun the tests.
at this test:
...
testMergeHistory (peak.storage.tests.test_undo.HistoryTests) ... ok
testBasics (peak.storage.tests.test_undo.UndoTests) ... ok
testUndoRedo (peak.storage.tests.test_undo.UndoTests) ... ok
**checkConversions (peak.storage.tests.LDAP.LDAPSchemaTest) ...
the process hangs and eats all mem and cpu.
Tasks: 153 total, 5 running, 148 sleeping, 0 stopped, 0 zombie
Cpu(s): 51.3% user, 8.2% system, 0.0% nice, 40.5% idle
Mem: 645052k total, 640904k used, 4148k free, 3240k buffers
Swap: 2056272k total, 837892k used, 1218380k free, 11676k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8208 root 17 0 677m 568m 563m R 53.5 90.2 19:51.96 peak
8121 jack 9 0 9156 6224 6192 R 2.3 1.0 0:06.93 kdeinit
8316 jack 13 0 1004 1004 756 R 1.3 0.2 0:00.47 top
one needs to kill -9 the process to end it.
i have python-ldap installed
python-packages installed:
----------------------------------
python2.3 2.3.5-2
python2.3-cheetah 0.9.16-0
python2.3-crypto 2.0+dp1-2
python2.3-dev 2.3.5-2
python2.3-doc 2.3.5-2
python2.3-egenix-mxdatetime 2.0.6-1
python2.3-egenix-mxtools 2.0.6-1
python2.3-extclass 1.2.0zope-2.5.1-1.3
python2.3-fchksum 1.7.1-1
python2.3-gadfly 1.0.0-7
python2.3-gdbm 2.3.5-2
python2.3-imaging 1.1.4-3
python2.3-imaging-sane 1.1.4-3
python2.3-imaging-tk 1.1.4-3
python2.3-ldap 2.0.4-1
python2.3-maxdb 7.5.00.24-1
python2.3-mpz 2.3.5-2
python2.3-mysqldb 1.2.0-4
python2.3-numeric 23.8-1
python2.3-opengl 2.0.1.08-5.1
python2.3-pam 0.4.2-10.1
python2.3-pgsql 2.4.0-5
python2.3-psycopg 1.1.18-1
python2.3-pygresql 3.6.1-1
python2.3-pyopenssl 0.6-2
python2.3-pyrex 0.9.3-1
python2.3-reportlab 1.20debian-1
python2.3-subversion 1.1.4-1
python2.3-tk 2.3.5-2
python2.3-twisted 1.3.0-8
python2.3-twisted-bin 1.3.0-8
python2.3-twisted-conch 1.3.0-8
python2.3-xml 0.8.4-1
python2.3-xmms 2.04-2
what should i do to help you tracking down the problem ?
cheers
Ulrich
More information about the PEAK
mailing list