[issue13390] Hunt memory allocations in addition to reference leaks
STINNER Victor
report at bugs.python.org
Fri Dec 2 02:11:58 CET 2011
STINNER Victor <victor.stinner at haypocalc.com> added the comment:
The overhead on PyObject_Malloc() is just an increment on an integer, so it is very low (or null).
The feature is interesting, but I'm not convinced that a very simple counter is enough to track memory leaks. It may help the CPython test suite, but what about real world application?
> I think we should hide at least the initial implementation
> behind PY_REF_DEBUG until we're sure we've worked the kinks
> out of it.
Programs not always behave exactly the same in debug or in release mode. Sometimes, bugs disappear in debug mode :-(
If the feature is written to track memory leaks in the CPython test suite, it's ok to only expose the function in debug mode.
> Right now this patch will allow to enrich the daily refleak runs
Did you already found real leaks using your hack^Wpatch? (was c6dafa2e2594 found by your tool?)
----------
nosy: +haypo
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13390>
_______________________________________
More information about the Python-bugs-list
mailing list