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.21:28:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502400493.78.0.531235738135.issue31130@psf.upfronthosting.co.za>
In-reply-to
Content
> test_idle leaked [1, 1, 1, 1] memory blocks, sum=4

While reference leaks are more or less stable, the check on memory blocks is fragile.

I'm unable to reproduce your issue on Linux. I tested "./python -m test -R 3:3 -u gui -v test_idle". If you have a reproductible failure, please open a new issue since this one is closed.

If you consider that it's a recent regression, you can go back in history using git checkout <old sha1>, or even git bisect.

If you open a new issue, you may want to use "python -m test.bisect ..." to identify which test leaks memory blocks.
History
Date User Action Args
2017-08-10 21:28:13vstinnersetrecipients: + vstinner, terry.reedy
2017-08-10 21:28:13vstinnersetmessageid: <1502400493.78.0.531235738135.issue31130@psf.upfronthosting.co.za>
2017-08-10 21:28:13vstinnerlinkissue31130 messages
2017-08-10 21:28:13vstinnercreate