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 tim.peters
Recipients A. Skrobov, pitrou, tim.peters
Date 2015-03-06.15:52:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425657140.23.0.754154007139.issue23592@psf.upfronthosting.co.za>
In-reply-to
Content
Nothing should ever crash the interpreter :-)  So this is a thoroughly legitimate bug report.

However, there's no way to guess whether _this_ crasher is easy to fix, or next to impossible.  Without a test program to provoke the error, there's little to go on.  If it were a common problem with daemon threads, I'd expect at least several reports of similar behavior over the decades.  So chances seem to favor that there's something unique about the specifics of what your daemon threads were doing to provoke it - and/or timing quirks specific to your platform.
History
Date User Action Args
2015-03-06 15:52:20tim.peterssetrecipients: + tim.peters, pitrou, A. Skrobov
2015-03-06 15:52:20tim.peterssetmessageid: <1425657140.23.0.754154007139.issue23592@psf.upfronthosting.co.za>
2015-03-06 15:52:20tim.peterslinkissue23592 messages
2015-03-06 15:52:19tim.peterscreate