[3.8] bpo-39959: Do not use resource_tracker for shared_memory #20136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix the issue with "multiprocessing.shared_memory.SharedMemory" class registering open shared memory with resource_tracker, causing shared memory clean up after any of the connecting processes exit. The idea is not to use the resource_tracker at all and let the user be responsible for shared memory clean up. This allows shared memory to persist even if either the creating or any other reading processes have long exited.
https://bugs.python.org/issue39959
shm.py
https://bugs.python.org/issue39959