[issue11849] glibc allocator doesn't release all free()ed memory

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

Well, memory fragmentation can happen with any allocation scheme, and it's possible even Python 3 isn't immune to this.  Backporting performance improvements is a strain on our resources and also constitutes a maintenance threat (what if the bug hides in the new code?).  And Python 2.7 is really nearing its end-of-life more and more everyday.  So IMHO it's a no-no.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue11849>
_______________________________________