RAM consumption too high using concurrent.futures (Python 3.7 / 3.6 )

Open

#78,349 opened on Jul 20, 2018 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: python
Domain: backend

Research direction

Start with the concurrent.futures implementation and the five tracker messages linked in the report, focusing on the reported Python 3.6 and 3.7 behavior. Reproduce the RAM usage before choosing a change; done means the excessive consumption is explained and a verified fix or clearly documented limitation is established.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib topic-multiprocessing

BPO	34168
Nosy	@tim-one, @MojoVampire, @DemGiran

^{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 2018-07-20.12:53:50.593>
labels = ['3.7', 'library']
title = 'RAM consumption too high using concurrent.futures (Python 3.7 / 3.6 )'
updated_at = <Date 2018-07-25.17:37:22.027>
user = 'https://github.com/DemGiran'

bugs.python.org fields:

activity = <Date 2018-07-25.17:37:22.027>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-07-20.12:53:50.593>
creator = 'DemGiran'
dependencies = []
files = []
hgrepos = []
issue_num = 34168
keywords = []
message_count = 5.0
messages = ['322004', '322005', '322031', '322075', '322373']
nosy_count = 3.0
nosy_names = ['tim.peters', 'josh.r', 'DemGiran']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue34168'
versions = ['Python 3.6', 'Python 3.7']

Dominant language: Python
Stars: 77.2k
Forks: 36k
Avg merge: 1d 9h
Merged PRs (30d): 558

Contributor guide

Open the contributing 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.

Similar issues

[Correction] Update dsh-archived-chats metadata for Archive Management 1.4.1 Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

fendouai/awesome-deepseek-harness#88 · Opened Sep 21, 2026
[18.0+] account_edi_ubl_cii: IBR-022 wrongly reports "Invoiced quantity is missing" for invoice lines with quantity 0 Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

odoo/odoo#289575 · Opened Sep 21, 2026
Document TVD reference dependency in `create_rft_ertobs` Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

equinor/fmu-tools#514 · Opened Sep 21, 2026
`WandbCallback` config formatting fails on primitive values after #4164 Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

fastai/fastai#4173 · Opened Sep 21, 2026
[Bug] 发布机 Chrome applet 1.3 打开双语 Web 资产变英文（zh-hans 语言码不命中 zh-CN） Open

🐛 Bug 🔔 Pending processing

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

jumpserver/jumpserver#17584 · Opened Sep 21, 2026

More Python issues