[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-01-11 Thread David Chevell
Change by David Chevell : -- keywords: +patch, patch pull_requests: +11075, 11076 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-01-11 Thread David Chevell
Change by David Chevell : -- keywords: +patch, patch, patch pull_requests: +11075, 11076, 11077 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-01-11 Thread David Chevell
Change by David Chevell : -- keywords: +patch pull_requests: +11075 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35715> ___ ___ Py

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-01-11 Thread David Chevell
Change by David Chevell : -- keywords: +patch, patch, patch, patch pull_requests: +11075, 11076, 11077, 11078 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

2019-01-11 Thread David Chevell
New submission from David Chevell : ProcessPoolExecutor workers will hold onto the return value of their last task in memory until the next task is received. Since the return value has already been propagated to the parent process's `Future` or else effectively discarded, this is ho