➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients davin, larry, serhiy.storchaka, vstinner
Date 2017-10-25.13:55:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508939711.92.0.213398074469.issue31626@psf.upfronthosting.co.za>
In-reply-to
Content 
> Using nested _PyMem_DebugRawRealloc() looks suspicions to me. This may be a bug.

PyObject_Malloc() calls PyMem_RawMalloc() for allocations larger than 512 bytes.

When debug hooks are enabled, PyObject_Malloc() and PyMem_RawMalloc() both call _PyMem_DebugRawRealloc(). The behaviour that you saw is expected.

It was simpler to reuse _PyMem_DebugRawRealloc() PyObject and PyMem_Raw allocator families, rather than duplicating the code.
History
Date User Action Args
2017-10-25 13:55:11vstinnersetrecipients: + vstinner, larry, serhiy.storchaka, davin
2017-10-25 13:55:11vstinnersetmessageid: <1508939711.92.0.213398074469.issue31626@psf.upfronthosting.co.za>
2017-10-25 13:55:11vstinnerlinkissue31626 messages
2017-10-25 13:55:11vstinnercreate