Leak of locks from multiprocessing.Process
Open
Nobody has claimed this yet.
3.11
topic-C-API
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43145 |
|---|---|
| Nosy | @pitrou, @applio, @shihai1991, @YannickJadoul, @bstaletic |
| 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 2021-02-06.13:02:37.289>
labels = ['expert-C-API', '3.11', 'performance']
title = 'Leak of locks from multiprocessing.Process'
updated_at = <Date 2021-07-24.07:52:25.721>
user = 'https://github.com/bstaletic'
bugs.python.org fields:
activity = <Date 2021-07-24.07:52:25.721>
actor = 'shihai1991'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2021-02-06.13:02:37.289>
creator = 'bstaletic'
dependencies = []
files = ['49793', '50177']
hgrepos = []
issue_num = 43145
keywords = []
message_count = 4.0
messages = ['386558', '386559', '386774', '398121']
nosy_count = 5.0
nosy_names = ['pitrou', 'davin', 'shihai1991', 'YannickJadoul', 'bstaletic']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue43145'
versions = ['Python 3.11']
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 attached log and valgrind output.txt, then trace the multiprocessing.Process lock lifecycle through the CPython C API. The payload names no source file or test; done means reproducing the leak and confirming that process-created locks are released without new valgrind errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100