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 serhiy.storchaka
Recipients serhiy.storchaka, vstinner
Date 2018-10-23.19:36:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540323419.75.0.788709270274.issue35056@psf.upfronthosting.co.za>
In-reply-to
Content
Would be nice to add a possibility to test memory leaks if memory is allocated not by Python allocators, but inside external libraries. This would allow to catch leaks on the bridge between Python and external libraries. See for example issue34794.
History
Date User Action Args
2018-10-23 19:36:59serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner
2018-10-23 19:36:59serhiy.storchakasetmessageid: <1540323419.75.0.788709270274.issue35056@psf.upfronthosting.co.za>
2018-10-23 19:36:59serhiy.storchakalinkissue35056 messages
2018-10-23 19:36:59serhiy.storchakacreate