GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — [3.9] [3.10] gh-90622: Do not spawn ProcessPool workers on demand via fork method. (GH-91598) (GH-92497) by miss-islington · Pull Request #92499 · python/cpython Conversation
|
|
@gpshead: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@gpshead: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
… fork method. (pythonGH-91598) (pythonGH-92497) (python#92499) Do not spawn ProcessPool workers on demand when they spawn via fork. This avoids potential deadlocks in the child processes due to forking from a multithreaded process.. (cherry picked from commit ebb37fc) Co-authored-by: Gregory P. Smith <[email protected]> (cherry picked from commit b795376) Co-authored-by: Gregory P. Smith <[email protected]> Co-authored-by: Gregory P. Smith <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
concurrent.futures.ProcessPoolExecutor can deadlock when tcmalloc is used
There was an error while loading. Please reload this page.