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 terry.reedy, vstinner
Date 2017-08-10.22:58:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> As I said, I only get the 1 block leak with a micro test of a class or method.

Yeah, again, the memory block check is fragile. It might be an legit internal cache filled for good reasons. It can be a free list. It can be a lot of things. It's really hard to track such very tiny memory allocation. "leaked [1, 1, 1, 1] memory blocks" can be a false alarm, it's not big.
Date User Action Args
2017-08-10 22:58:52vstinnersetrecipients: + vstinner, terry.reedy
2017-08-10 22:58:52vstinnersetmessageid: <>
2017-08-10 22:58:52vstinnerlinkissue31130 messages
2017-08-10 22:58:51vstinnercreate