[issue33444] Memory leak/high usage on copy in different thread

whitespacer added the comment: pitrou, thanks for great diagnosing program! You are right that there is no memory leak. We have investigated this issue a little bit more - it looks real reason for large memory consuming in the end is not fragmentation, just glibc doesn't

[issue33444] Memory leak/high usage on copy in different thread

Change by Antoine Pitrou : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue33444] Memory leak/high usage on copy in different thread

Antoine Pitrou added the comment: Yes, this looks surprising, but there is no memory leak here, just memory fragmentation in the glibc allocator. This is the program I used to diagnose it: https://gist.github.com/pitrou/6c5310d4c721436165666044e3c31158 At the end the program

[issue33444] Memory leak/high usage on copy in different thread

Change by Serhiy Storchaka : -- nosy: +bquinlan, pitrou ___ Python tracker ___

[issue33444] Memory leak/high usage on copy in different thread

New submission from MultiSosnooley : On linux (ubuntu 16.04, 18.04 tested) with python 3.6.5, 3.5.5 and 3.7-dev (windows is not affected) there is ~850Mb of memory used by python process at sleep point. Replacing `submit` `result` with plain function call causes