Issue 3541: bsddb memory leak on ubuntu (original) (raw)

Created on 2008-08-11 13:06 by kcwu, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg71013 - (view) Author: Kuang-che Wu (kcwu) Date: 2008-08-11 13:06
On ubuntu, python 2.5.2. The memory usage of following program is increasing infinitly. There may be something leaking. However, it only consumes constant memory on windows (python 2.5.2). import bsddb d = bsddb.hashopen('a.db', 'c') d.close() while True: d = bsddb.hashopen('a.db') d.close()
msg87931 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-05-16 21:00
Confirmed in trunk.
msg87934 - (view) Author: Marcin Bachry (marcin.bachry) Date: 2009-05-16 21:17
The test program uses constant memory on my machine. Ubuntu 9.04, libdb4.7.25-6ubuntu1, python 2.7 trunk.
msg88046 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2009-05-18 19:57
Python 2.5 is in security maintenance mode only. Please, upgrade to Python 2.6. If you can not upgrade Python, install a recent bsddb release from http://www.jcea.es/programacion/pybsddb.htm If you can still reproduce the problem, let me know.
msg88054 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-05-18 21:39
I can confirm it in trunk and release26-maint on Ubuntu 8.04. For trunk: bsddb.__version__ : '4.7.3' libdb4.6-dev: 4.6.21-6ubuntu1 _bsddb.version(): (4, 6, 21) bsddb._bsddb.cvsid: '$Id: _bsddb.c 66568 2008-09-23 18:54:08Z jesus.cea $'
msg88193 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2009-05-22 12:17
I can *not* reproduce the problem with Python 2.6 (with its stock bsddb version) and Berkeley DB 4.7.25 (the current one). I can reproduce the issue if I use Berkeley DB 4.6.21. Seems to be a (solved) problem in the library. Berkeley DB 4.7.25 is known to solve a few memory leaks: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html I mark the bug as "closed" and "out of date" because it is no something we can solve and it is already resolved in BDB 4.7.25, published a year ago. Moreover, any serious usage of Berkeley DB "demands" a recent version of the library.
History
Date User Action Args
2022-04-11 14:56:37 admin set github: 47791
2009-05-22 12:17:16 jcea set status: open -> closedassignee: jcea -> resolution: out of datemessages: +
2009-05-18 21:39:34 ajaksu2 set status: closed -> openresolution: out of date -> (no value)messages: + versions: + Python 2.7
2009-05-18 19:57:53 jcea set status: open -> closedassignee: jcearesolution: out of datemessages: +
2009-05-16 21:17:04 marcin.bachry set nosy: + marcin.bachrymessages: +
2009-05-16 21:00:06 ajaksu2 set priority: normalversions: + Python 2.6, - Python 2.5nosy: + ajaksu2, jceamessages: + stage: test needed
2008-08-11 13:06:46 kcwu create