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 Albert.Zeyer, neologix, pitrou, r.david.murray
Date 2013-02-23.22:27:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> - how do you know the crash really happens because of thread 5?

All other threads are blocked on locks or condition variables, it's
the only runnable thread.

> Another question: are threads being started or stopped while the thread local object is being deleted?

From the stack trace, thread 2 is being stopped.

I guess the problem is similar to above: thread 2 is in the middle of
stopping, its TLS dict is deallocated, which triggers the thread local
object deallocation, which releases the GIL. Thread 5 becomes running,
and must somehow access thread 2 tstate.
It would be much easier with a backtrace, though.
Date User Action Args
2013-02-23 22:27:34neologixsetrecipients: + neologix, pitrou, r.david.murray, Albert.Zeyer
2013-02-23 22:27:34neologixlinkissue17263 messages
2013-02-23 22:27:34neologixcreate