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 — Use stop-the-world to make fork and interpreter shutdown thread-safe · Issue #116522 · python/cpython Closed Assignees Labels DescriptionFeature or enhancementIn the free-threaded build, we should use a stop-the-world call to make The two operations are similar in that they both involve deleting thread states for other threads. ForkFork and in multithreaded environments is notorious for the problems it causes, but we can make the free-threaded build at least as safe as the default (GIL) build by pausing other threads with a stop-the-world call before forking. In the parent, we can use a normal start-the-world call to resume other threads after fork. In the child, we want to call start the world after other thread states are removed, but before we execute python code. This may require some refactoring. ShutdownThe interpreter waits for threading module created non-daemon threads during shutdown, but this can be canceled by a Linked PRs
Footnotes
Activity
MetadataMetadataAssigneesLabelsProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |