[New-bugs-announce] [issue26418] multiprocessing.pool.ThreadPool eats up memories

[renlifeng]

New submission from renlifeng:

If func creates lots objects and appends them to a list, and runs over and over, pool.map(func...) will eventually eat up all memories. Cleaning the list at the end of func does not help.

One can reproduce by running the attached file.

By contrast, after replacing ThreadPool with the theading module (see the commented out lines), memory usage will not grow continuously.

By the way, I used what's in Debian stretch, i.e. python 2.7.11 and 3.5.1.

----------
components: Library (Lib)
files: cvtest5.py
messages: 260716
nosy: renlifeng
priority: normal
severity: normal
status: open
title: multiprocessing.pool.ThreadPool eats up memories
versions: Python 2.7, Python 3.5
Added file: http://bugs.python.org/file42012/cvtest5.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26418>
_______________________________________