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 vstinner
Date 2018-10-23.16:42:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540312934.43.0.788709270274.issue35053@psf.upfronthosting.co.za>
In-reply-to
Content
CPython uses many "free lists": list of "deallocated" objects which are kept alive to optimize allocation of new objects. For example, the builtin list type has a free list.

Problem: tracemalloc only traces the memory allocation when the object is created, but it doesn't update the traceback when the "free object" is reused to create "a new object".

Attached PR modifies _Py_NewReference() to update the Python traceback in the tracemalloc trace.
History
Date User Action Args
2018-10-23 16:42:14vstinnersetrecipients: + vstinner
2018-10-23 16:42:14vstinnersetmessageid: <1540312934.43.0.788709270274.issue35053@psf.upfronthosting.co.za>
2018-10-23 16:42:14vstinnerlinkissue35053 messages
2018-10-23 16:42:14vstinnercreate