multiprocessing.Process file descriptor resource leak
Open
Nobody has claimed this yet.
docs
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39535 |
|---|---|
| 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 2020-02-03.09:21:12.039>
labels = ['docs', 'library', 'performance']
title = 'multiprocessing.Process file descriptor resource leak'
updated_at = <Date 2020-02-03.09:56:03.757>
user = 'https://bugs.python.org/RobertPierce'
bugs.python.org fields:
activity = <Date 2020-02-03.09:56:03.757>
actor = 'Robert Pierce'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2020-02-03.09:21:12.039>
creator = 'Robert Pierce'
dependencies = []
files = ['48878']
hgrepos = []
issue_num = 39535
keywords = []
message_count = 2.0
messages = ['361273', '361275']
nosy_count = 2.0
nosy_names = ['docs@python', 'Robert Pierce']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue39535'
versions = ['Python 3.6']
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 by running the linked proc_test.py script to reproduce the multiprocessing.Process file-descriptor leak, then trace the relevant multiprocessing.Process implementation in CPython. Done means the reproduction no longer leaks descriptors and the behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100