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 kristjan.jonsson
Recipients kristjan.jonsson, neologix, pitrou, sbt
Date 2013-05-13.16:14:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368461644.96.0.252040085832.issue17969@psf.upfronthosting.co.za>
In-reply-to
Content
Well, knowing that they crash less in 3.3 doesn't really fix the problem now, does it?

We can consider two options then:
1) A multiprocessing specific fix.  Removing this handle close gil release (which is superfluous, since these calls aren't blocking in any real sense) will certainly remove _this_ instance of the crash.  An alternative is to make this worker thread non-daemon.  That shouldn't be too hard and shouldn't have any other side effects.

2) A general daemon thread fix.  For example, removing the GIL at the start of the shutdown process will make it impossible to release it.  We can do this by setting interpreter_lock to NULL.

I don't see the point of having 2.7 in bug fix mode if we can't fix bugs.
History
Date User Action Args
2013-05-13 16:14:05kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, neologix, sbt
2013-05-13 16:14:04kristjan.jonssonsetmessageid: <1368461644.96.0.252040085832.issue17969@psf.upfronthosting.co.za>
2013-05-13 16:14:04kristjan.jonssonlinkissue17969 messages
2013-05-13 16:14:04kristjan.jonssoncreate