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 ncoghlan
Recipients ncoghlan, neologix, vstinner, zach.ware
Date 2014-08-13.06:42:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407912175.87.0.645515613061.issue22190@psf.upfronthosting.co.za>
In-reply-to
Content
Trying to debug issue #22166, I realised it would be nice if there was an easy way to use tracemalloc to get a clear idea of *what's* leaking when regrtest -R reports a refleak.

For that specific issue, I'm just trying to hack something together as a learning experience, but it would be good to have something more sophisticated built in to regrtest.
History
Date User Action Args
2014-08-13 06:42:55ncoghlansetrecipients: + ncoghlan, vstinner, neologix, zach.ware
2014-08-13 06:42:55ncoghlansetmessageid: <1407912175.87.0.645515613061.issue22190@psf.upfronthosting.co.za>
2014-08-13 06:42:55ncoghlanlinkissue22190 messages
2014-08-13 06:42:55ncoghlancreate