Message293435
Any update on this reviewing, patching, and then backporting to 2.7? We've just run into the exact same issue here in Google using a ThreadPoolExecutor.map call growing memory usage without bounds due to the Future holding onto its result even after being returned from the map call. There's a more specific patch possible for just map() itself, but this more general one seems like it'd be better. |
|
Date |
User |
Action |
Args |
2017-05-10 16:42:23 | Mark DePristo | set | recipients:
+ Mark DePristo, bquinlan, grzgrzgrz3, rnester, willvousden |
2017-05-10 16:42:23 | Mark DePristo | set | messageid: <1494434543.32.0.524546544138.issue27144@psf.upfronthosting.co.za> |
2017-05-10 16:42:23 | Mark DePristo | link | issue27144 messages |
2017-05-10 16:42:23 | Mark DePristo | create | |
|