Message 322230 - Python tracker

➜

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	tzickel
Recipients	Windson Yang, davin, docs@python, mattip, pitrou, tzickel, zach.ware
Date	2018-07-23.16:26:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1532363206.63.0.56676864532.issue34172@psf.upfronthosting.co.za>
In-reply-to

Content
I think I've found the code bug causing the leak: https://github.com/python/cpython/blob/caa331d492acc67d8f4edd16542cebfabbbe1e79/Lib/multiprocessing/pool.py#L180 There is a circular reference between the Pool object, and the self._worker_handler Thread object (and it's also saved in the frame locals for the thread object, which prevents it from being garbage collected).

I think I've found the code bug causing the leak:

https://github.com/python/cpython/blob/caa331d492acc67d8f4edd16542cebfabbbe1e79/Lib/multiprocessing/pool.py#L180

There is a circular reference between the Pool object, and the self._worker_handler Thread object (and it's also saved in the frame locals for the thread object, which prevents it from being garbage collected).

History
Date	User	Action	Args
2018-07-23 16:26:46	tzickel	set	recipients: + tzickel, pitrou, docs@python, zach.ware, mattip, davin, Windson Yang
2018-07-23 16:26:46	tzickel	set	messageid: <1532363206.63.0.56676864532.issue34172@psf.upfronthosting.co.za>
2018-07-23 16:26:46	tzickel	link	issue34172 messages
2018-07-23 16:26:46	tzickel	create