➜

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 Mark.Shannon, davin, ned.deily, pitrou, serhiy.storchaka, vstinner
Date 2018-05-23.10:30:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527071409.32.0.682650639539.issue33612@psf.upfronthosting.co.za>
In-reply-to
Content 
I created PR 7069 to remove the assertion. With this change, attached bug.py doesn't crash anymore, but it still logs warnings in verbose mode:

vstinner@apu$ ./python -v bug.py 
(...)
PyThreadState_Clear: warning: thread still has a frame
PyThreadState_Clear: warning: thread still has a frame
PyThreadState_Clear: warning: thread still has a generator
PyThreadState_Clear: warning: thread still has a frame
PyThreadState_Clear: warning: thread still has a generator
PyThreadState_Clear: warning: thread still has a frame

The root issue is that Python doesn't join deamonic threads. But it's by design no?

I hate daemonic threads :-)

For the specific case of a fork(), it can be possible that a thread calls os.fork() while another thread is running a generator, no?

--

Since this issue seems to be a regression and I have a PR fixing it, I propose to mark this issue as a release blocker. Sorry Ned :-(
History
Date User Action Args
2018-05-23 10:30:09vstinnersetrecipients: + vstinner, pitrou, ned.deily, Mark.Shannon, serhiy.storchaka, davin
2018-05-23 10:30:09vstinnersetmessageid: <1527071409.32.0.682650639539.issue33612@psf.upfronthosting.co.za>
2018-05-23 10:30:09vstinnerlinkissue33612 messages
2018-05-23 10:30:09vstinnercreate