[issue26850] PyMem_RawMalloc(): update also sys.getallocatedblocks() in debug mode

2016-05-20 Thread STINNER Victor
STINNER Victor added the comment: I'm not convinced myself by this change, it may make detection of memory leaks much more tricky for a little gain. I prefer to reject my own issue ;-) -- resolution: -> rejected status: open -> closed ___ Python tra

[issue26850] PyMem_RawMalloc(): update also sys.getallocatedblocks() in debug mode

2016-04-26 Thread STINNER Victor
STINNER Victor added the comment: The expected side effect of this change is that hunting memory leaks in regrtest (python -m test) may get more noise. I ran the Python test suite using "./python -m test -R 3:3": test_nntplib, test_tools and test_unittest failed. Run alone, test_tools still f

[issue26850] PyMem_RawMalloc(): update also sys.getallocatedblocks() in debug mode

2016-04-26 Thread STINNER Victor
New submission from STINNER Victor: I modified PyMem_Malloc() to use the pymalloc allocator in the issue #26249. This change helped to find a memory leak in test_format that I introduced in Python 3.6: http://bugs.python.org/issue26249#msg264174 This memory leak gave me an idea: PyMem_RawMallo