This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author renlifeng
Recipients renlifeng
Date 2016-02-23.09:47:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456220840.03.0.74121216833.issue26418@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-02-23 09:47:20renlifengsetrecipients: + renlifeng
2016-02-23 09:47:20renlifengsetmessageid: <1456220840.03.0.74121216833.issue26418@psf.upfronthosting.co.za>
2016-02-23 09:47:19renlifenglinkissue26418 messages
2016-02-23 09:47:19renlifengcreate