[issue18404] Memory leak in gdbmmodule

2013-10-25 Thread Christian Heimes
Christian Heimes added the comment: The problem is already fixed in 3.3 and 3.4. Thank you nevertheless! :) -- nosy: +christian.heimes resolution: -> out of date stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue18404] Memory leak in gdbmmodule

2013-07-16 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue18404] Memory leak in gdbmmodule

2013-07-09 Thread Christian Heimes
Changes by Christian Heimes : -- nosy: +haypo stage: -> patch review type: -> resource usage versions: +Python 3.4 ___ Python tracker ___ __

[issue18404] Memory leak in gdbmmodule

2013-07-09 Thread Bohuslav "Slavek" Kabrda
Bohuslav "Slavek" Kabrda added the comment: I just tried rebuilding with my patch and running test suite + I did some manual testing and everything seems to work fine - and the memory leak is not there. -- ___ Python tracker

[issue18404] Memory leak in gdbmmodule

2013-07-08 Thread Bohuslav "Slavek" Kabrda
New submission from Bohuslav "Slavek" Kabrda: Function dbm_length from Modules/_gdbmmodule.c seems to be leaking memory. A simple reproducer: import dbm d = dbm.open('spam', 'c') d['x'] = '1' print(len(d)) The interesting part of valgrind output with --leak-check=full: ==3312== 1 bytes in 1