resource tracker destroys shared memory segments when other processes should still have valid access
Open
@applio is already working on this.
Since Sep 11, 2019.
docs
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38119 |
|---|---|
| Nosy | @pitrou, @applio, @pablogsal, @maggyero, @vinay0410, @JSmith-BitFlipper, @keven425, @TKaluza |
| PRs | |
| Files |
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:
assignee = 'https://github.com/applio'
closed_at = None
created_at = <Date 2019-09-11.15:58:26.817>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'resource tracker destroys shared memory segments when other processes should still have valid access'
updated_at = <Date 2022-02-10.20:53:56.777>
user = 'https://github.com/applio'
bugs.python.org fields:
activity = <Date 2022-02-10.20:53:56.777>
actor = 'maggyero'
assignee = 'davin'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-09-11.15:58:26.817>
creator = 'davin'
dependencies = []
files = ['49859']
hgrepos = []
issue_num = 38119
keywords = ['patch']
message_count = 14.0
messages = ['351960', '352050', '374434', '374939', '374944', '374951', '374954', '374956', '374958', '374974', '387606', '388287', '390198', '412440']
nosy_count = 12.0
nosy_names = ['pitrou', 'steve.newcomb', 'turicas', 'davin', 'pablogsal', 'maggyero', 'vinay0410', 'damian.barabonkov', 'keven425', 'davfelsen', 'jdogzz-g5', 'timka']
pr_nums = ['15989', '21516', '23174']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38119'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
TODO list:
- Add a
track=Trueparameter to SharedMemory (#110778 did this) so it can be disabled by the user. - It still needs covering in the What's New in 3.13 documentation.
- Verify and make other documentation improvements as necessary as alluded by @ambv below in https://github.com/python/cpython/issues/82300#issuecomment-1336166761 - It sounded like we've got docs implying that resources outlive the process by default which was not what the implementation ever did.
Linked PRs
- gh-110778
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.