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 neologix
Recipients Arfrever, neologix, pitrou, python-dev, serhiy.storchaka, vajrasky, vstinner
Date 2013-12-13.08:30:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Correct me if I'm wrong, but destroying the thread state of daemon threads
while they're running is really a bad idea in fact: for example, if
warnings are now emitted for unclosed file objects, this means that the
file object, and all associated buffers, are destroyed.
But even though the daemon thread doesn't hold the GIL, he might still be
using this object.

For example, if we have:
daemon thread:
    read(fd, fileobj->buffer, fileobj->size)

and the main thread exits, then fileobj will be deallocated.

It's actually fairly easy to write a short crasher launching a deamon
thread reading from e.g. /dev/zero in loop, with the main thread exiting
right in the middle.
Date User Action Args
2013-12-13 08:30:38neologixsetrecipients: + neologix, pitrou, vstinner, Arfrever, python-dev, serhiy.storchaka, vajrasky
2013-12-13 08:30:38neologixlinkissue19466 messages
2013-12-13 08:30:37neologixcreate