Repository navigation
SharedMemoryManager should relase its resources when its parent process dies #81158
Description
| BPO | 36977 |
|---|---|
| Nosy | @pitrou, @applio, @pierreglaser |
| PRs |
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-05-20.20:00:33.967>
labels = ['library']
title = 'SharedMemoryManager should relase its resources when its parent process dies'
updated_at = <Date 2019-05-20.20:21:56.871>
user = 'https://github.com/pierreglaser'bugs.python.org fields:
activity = <Date 2019-05-20.20:21:56.871>
actor = 'pierreglaser'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-05-20.20:00:33.967>
creator = 'pierreglaser'
dependencies = []
files = []
hgrepos = []
issue_num = 36977
keywords = ['patch']
message_count = 1.0
messages = ['342948']
nosy_count = 3.0
nosy_names = ['pitrou', 'davin', 'pierreglaser']
pr_nums = ['13451']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36977'
versions = []
Activity
pierreglaser commentedon May 20, 2019
The new multiprocessing.managers.SharedMemoryManager spawns a server that delivers memory segments to a parent Python process. If the parent process terminates unexpectedly, we should now make the manager process notice this termination it using the recent multiprocessing.parent_process object (that comes with a sentinel), and shut it down.