Potential Memory leak with concurrent.futures.ThreadPoolExecutor's map #85754
Description
| BPO | 41588 |
|---|---|
| Nosy | @brianquinlan, @pitrou, @aeros |
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-08-19.13:55:15.731>
labels = ['extension-modules', '3.7', 'performance']
title = "Potential Memory leak with concurrent.futures.ThreadPoolExecutor's map"
updated_at = <Date 2020-10-29.20:55:16.766>
user = 'https://bugs.python.org/or12'bugs.python.org fields:
activity = <Date 2020-10-29.20:55:16.766>
actor = 'aeros'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2020-08-19.13:55:15.731>
creator = 'or12'
dependencies = []
files = []
hgrepos = []
issue_num = 41588
keywords = []
message_count = 1.0
messages = ['375647']
nosy_count = 4.0
nosy_names = ['bquinlan', 'pitrou', 'aeros', 'or12']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue41588'
versions = ['Python 3.7']