[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- title: Possible Memory Leak with 'shelve' - bsddb memory leak on Mac OS X 10.9 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22534 ___

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread TJ
TJ added the comment: No issue with 3.4 on the Mac box. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22534 ___ ___ Python-bugs-list mailing

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - ronaldoussoren components: +Extension Modules, Macintosh -Library (Lib) nosy: +ronaldoussoren type: - resource usage ___ Python tracker rep...@bugs.python.org

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread STINNER Victor
STINNER Victor added the comment: [10:55:57] ~$ python -c import anydbm;d = anydbm.open('bla', 'c');print(type(d)) class 'bsddb._DBWithCursor' Hum, on Mac OS X, I don't have the bsddb module installed by default. How did you install it? -- ___

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread Ned Deily
Ned Deily added the comment: Thanks for the detailed information. I'm not able to reproduce on OS X 10.9.5 with the python.org Python 2.7.8 which builds and links with its own copy of Sleepycat DB 4.7.25. However, I do see the memory leak when using a MacPorts Python 2.7.8 that is linked

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread TJ
TJ added the comment: I should have mentioned that this a Macports environment. So python, bsddb all come from there. Looks like that might be the culprit. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22534

[issue22534] bsddb memory leak on Mac OS X 10.9

2014-10-02 Thread Ned Deily
Ned Deily added the comment: Yeah, and I'm not sure why they have their build pegged to bdb 4.6; they provide newer ports as well. I think we can close this issue then. Perhaps you could open a MacPorts issue and ask them to update their python27 port to use at least db47. --