Multiprocessing shared_memory ValueError on race with ShareableList
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37652 |
|---|---|
| Nosy | @pitrou, @applio, @bensimner, @pierreglaser, @mental32 |
| 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 = None
closed_at = None
created_at = <Date 2019-07-22.15:13:18.222>
labels = ['type-bug', '3.8', '3.9']
title = 'Multiprocessing shared_memory ValueError on race with ShareableList'
updated_at = <Date 2019-09-11.17:44:09.596>
user = 'https://github.com/bensimner'
bugs.python.org fields:
activity = <Date 2019-09-11.17:44:09.596>
actor = 'davin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-07-22.15:13:18.222>
creator = 'bjs'
dependencies = []
files = ['48496']
hgrepos = []
issue_num = 37652
keywords = []
message_count = 9.0
messages = ['348299', '348443', '348449', '348487', '348536', '348604', '348606', '351998', '352001']
nosy_count = 5.0
nosy_names = ['pitrou', 'davin', 'bjs', 'pierreglaser', 'mental']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37652'
versions = ['Python 3.8', 'Python 3.9']
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.
Research direction
Start with the linked test.py file and the multiprocessing shared_memory and ShareableList behavior described in the issue. Reproduce the race between shared-memory access and ShareableList cleanup, then inspect the relevant multiprocessing tests and implementation. Done means the race no longer produces the reported ValueError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100