Author vstinner
Recipients serhiy.storchaka, vstinner, xiang.zhang
Date 2018-10-26.10:27:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540549623.14.0.788709270274.issue35056@psf.upfronthosting.co.za>
In-reply-to
Content
About automation, regrtest -R checks memory leaks using sys.getallocatedblocks(). But this function only tracks PyMem_Malloc() and PyObject_Malloc() (which is now technically the same memory allocator, since Python 3.6: https://docs.python.org/dev/c-api/memory.html#default-memory-allocators )

I tried to track PyMem_RawMalloc() using regrtest but... the raw memory allocator is not really "deterministic", it's hard to get reliable behavior. See: bpo-26850.

Tracking memory leaks is an hard topic :-) I'm happy that I finally fixed tracemalloc to track properly objects in free lists: bpo-35053!
History
Date User Action Args
2018-10-26 10:27:03vstinnersetrecipients: + vstinner, serhiy.storchaka, xiang.zhang
2018-10-26 10:27:03vstinnersetmessageid: <1540549623.14.0.788709270274.issue35056@psf.upfronthosting.co.za>
2018-10-26 10:27:03vstinnerlinkissue35056 messages
2018-10-26 10:27:03vstinnercreate