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 jbfzs
Recipients jbfzs, r.david.murray, rhettinger, serhiy.storchaka, vstinner, Александр Карпинский
Date 2017-11-21.15:54:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511279641.2.0.213398074469.issue27535@psf.upfronthosting.co.za>
In-reply-to
Content
> But it will still "leak" when you display ResourceWarning warnings with an action different than "always". In this case, IMHO the root issue is more the code which doesn't close the resource, than Python itself.

Not closing a file is a bug, but under normal circumstances it causes no leak by itself. The fact that the warnings module leaks in this case seems a problem. Had I logged warnings correctly, I would have found the bug by looking at the application log rather than by investigating the cause of the OOM killer invocation.

IMHO, the warnings module should have upper bounds on memory consumption to avoid DOSing itself.
History
Date User Action Args
2017-11-21 15:54:01jbfzssetrecipients: + jbfzs, rhettinger, vstinner, r.david.murray, serhiy.storchaka, Александр Карпинский
2017-11-21 15:54:01jbfzssetmessageid: <1511279641.2.0.213398074469.issue27535@psf.upfronthosting.co.za>
2017-11-21 15:54:01jbfzslinkissue27535 messages
2017-11-21 15:54:01jbfzscreate