Message 339137 - Python tracker

➜

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	mocramis
Recipients	eric.snow, methane, mocramis
Date	2019-03-29.19:22:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1553887338.14.0.718217454357.issue36469@roundup.psfhosted.org>
In-reply-to

Content
Thank you a lot for this detailed answer. Does the "causes of exit" may terminate the thread without releasing the GIL ? Because as far as i can tell, none of the threads seems to own the GIL (i only checked _PyThreadState_Current though there might be a better way to find the GIL owner). Therefore, the question is whether thread B is still alive after tB2. and, if so, whether we can find it. (Or whether we can understand why it left without releasing the GIL). Is there any variable i may check to dig this further ?

Thank you a lot for this detailed answer.

Does the "causes of exit" may terminate the thread without releasing the GIL ?
Because as far as i can tell, none of the threads seems to own the GIL (i only checked _PyThreadState_Current though there might be a better way to find the GIL owner).
Therefore, the question is whether thread B is still alive after tB2. and, if so, whether we can find it. (Or whether we can understand why it left without releasing the GIL).

Is there any variable i may check to dig this further ?

History
Date	User	Action	Args
2019-03-29 19:22:18	mocramis	set	recipients: + mocramis, methane, eric.snow
2019-03-29 19:22:18	mocramis	set	messageid: <1553887338.14.0.718217454357.issue36469@roundup.psfhosted.org>
2019-03-29 19:22:18	mocramis	link	issue36469 messages
2019-03-29 19:22:18	mocramis	create