Skip to content

[core] Only one of the threads in a thread pool will be initialized as a long-running Python thread #51071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kevin85421 opened this issue Mar 4, 2025 · 0 comments · May be fixed by #52575
Assignees
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P0 Issues that should be fixed in short order

Comments

@kevin85421
Copy link
Member

kevin85421 commented Mar 4, 2025

What happened + What you expected to happen

Currently, only one of the threads in a thread pool will be initialized as a long-running Python thread. I should also investigate whether it's possible to call PyGILState_Release on a different thread other than the one calls PyGILState_Ensure in the thread pool.

Versions / Dependencies

TODO

Reproduction script

TODO

Issue Severity

None

@kevin85421 kevin85421 added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) core Issues that should be addressed in Ray Core and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Mar 4, 2025
@kevin85421 kevin85421 self-assigned this Mar 4, 2025
@edoakes edoakes added the P0 Issues that should be fixed in short order label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P0 Issues that should be fixed in short order
Projects
None yet
2 participants