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-26.13:14:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Wouldn't it be better to expose and re-use the HEAD_LOCK and HEAD_UNLOCK
> macros from pystate.c?

I don't like holding locks before calling "alien" code, it's a recipe
for deadlocks: for example, if another thread-local object was
deallocated as part of the deallocation chain, we would call back into
local_clear(), and deadlock.

> That said, I doubt this is the issue here. We are removing a string key pointing
> to a localdummy object. Both are small atomic types not handled by the GC, so
> I don't see how deallocating these objects could release the GIL.

Yes, it shouldn't happen, the thread local dict is deallocated right
before (I initially thought the thread local dict was deallocated

Without a proper backtrace, i'ts going to be hard to debug...
Date User Action Args
2013-02-26 13:14:53neologixsetrecipients: + neologix, pitrou, r.david.murray, Albert.Zeyer
2013-02-26 13:14:53neologixlinkissue17263 messages
2013-02-26 13:14:53neologixcreate