-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
ValueError exception on _winapi.WaitForMultipleObjects #84444
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
Labels
3.7 (EOL)
end of life
3.8 (EOL)
end of life
3.9
only security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
OS-windows
Comments
See attached reproducer |
See my proposed patch. I am happy to make a PR on github for this too if people agree it's the right fix. |
(Created from bpo-26903) Yeah, that looks like a reasonable fix :) |
This is still an issue in python3.9. It just hit us while using the default config on a Threadripper 3990X that has 128 logical cores: with concurrent.futures.ProcessPoolExecutor() as executor: |
Fixed, better late than never. |
This was referenced Jun 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.7 (EOL)
end of life
3.8 (EOL)
end of life
3.9
only security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
OS-windows
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: