Issue 1976: pybsddb leak in using cursors (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/46268

classification

Title: pybsddb leak in using cursors
Type: resource usage Stage:
Components: Extension Modules Versions: Python 2.6, Python 2.5

process

Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: gregory.p.smith Nosy List: gregory.p.smith, jcea, loewis
Priority: normal Keywords:

Created on 2008-01-30 16:48 by jcea, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (7)
msg61871 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2008-01-30 16:48
Iterating a cursor over a database seems to leak memory. See http://sourceforge.net/mailarchive/forum.php?thread_name=4797B7D0.8060701%40gmail.com&forum_name=pybsddb-users
msg61890 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2008-01-31 08:56
Seems to be a leak when a cursor is used in a database without an environment. Working on this...
msg61891 - (view) Author: Jesús Cea Avión (jcea) * (Python committer) Date: 2008-01-31 09:08
Memory leak solved. Commit 293 in Sourceforge
msg61919 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-01-31 18:05
Greg, can you take a look?
msg61920 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-01-31 18:06
jcea, can you please attach the actual patch to be reviewed to this report? What is commit 293 in SourceForge?
msg61969 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2008-02-01 18:04
yes i'll take a look at this weekend. jcea is doing his bsddb development in the pybsddb.sf.net project svn repository for the time being. I'll be merging his changes back into the python tree. We can get him python svn access soon but i wanted to make sure things were going smoothly first.
msg62022 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2008-02-03 08:17
Fix committed as r60544 in trunk and r60545 in release25-maint. i assume it'll be merged into py3k in the regular py3k merge sweeps.
History
Date User Action Args
2022-04-11 14:56:30 admin set github: 46268
2008-02-03 08:17:27 gregory.p.smith set status: open -> closedresolution: acceptedmessages: + versions: + Python 2.6, Python 2.5
2008-02-01 18:04:25 gregory.p.smith set messages: +
2008-01-31 18:06:22 loewis set messages: +
2008-01-31 18:05:20 loewis set assignee: gregory.p.smithmessages: + nosy: + gregory.p.smith, loewis
2008-01-31 09:08:46 jcea set messages: +
2008-01-31 08:56:05 jcea set messages: +
2008-01-30 16:48:47 jcea set type: resource usageseverity: normal -> major
2008-01-30 16:48:26 jcea create