➜

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 neologix, pitrou, skrah, vstinner
Date 2013-11-18.08:45:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384764345.55.0.668488489321.issue13090@psf.upfronthosting.co.za>
In-reply-to
Content 
If the result of os.read() was stored in a Python daemon thread, the memory should be released since the following changeset. Can someone check if this issue still exist?

changeset:   87070:c2a13acd5e2b
user:        Victor Stinner <victor.stinner@gmail.com>
date:        Tue Nov 12 16:37:55 2013 +0100
files:       Lib/test/test_threading.py Misc/NEWS Python/pythonrun.c
description:
Close #19466: Clear the frames of daemon threads earlier during the Python
shutdown to call objects destructors. So "unclosed file" resource warnings are
now corretly emitted for daemon threads.
History
Date User Action Args
2013-11-18 08:45:45vstinnersetrecipients: + vstinner, pitrou, skrah, neologix
2013-11-18 08:45:45vstinnersetmessageid: <1384764345.55.0.668488489321.issue13090@psf.upfronthosting.co.za>
2013-11-18 08:45:45vstinnerlinkissue13090 messages
2013-11-18 08:45:45vstinnercreate