Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Feb 20, 2018

The CPython runtime assumes that there is a one-to-one relationship (for a given interpreter) between PyThreadState and OS threads. Sending and receiving on a channel in the same interpreter was causing crashes because of this (specifically due to a check in PyThreadState_Swap()). The solution is to not switch threads if the interpreter is the same.
(cherry picked from commit f53d9f2)

Co-authored-by: Eric Snow ericsnowcurrently@gmail.com

https://bugs.python.org/issue32604

…gh-5778)

The CPython runtime assumes that there is a one-to-one relationship (for a given interpreter) between PyThreadState and OS threads. Sending and receiving on a channel in the same interpreter was causing crashes because of this (specifically due to a check in PyThreadState_Swap()). The solution is to not switch threads if the interpreter is the same.
(cherry picked from commit f53d9f2)

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>
@miss-islington
Copy link
Contributor Author

@ericsnowcurrently: Backport status check is done, and it's a success ✅ .

@ericsnowcurrently ericsnowcurrently merged commit eed3c7a into python:3.7 Feb 21, 2018
@miss-islington
Copy link
Contributor Author

Thanks, @ericsnowcurrently!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants