[issue20494] Backport of http://bugs.python.org/issue11849 to Python 2.7 (Make it more likely for the system allocator to release free()d memory arenas on glibc-based systems).

Changes by Benjamin Yolken : Removed file: http://bugs.python.org/file33883/memory_fix_updated.patch ___ Python tracker <http://bugs.python.org/issue20494> ___ ___ Pytho

[issue20494] Backport of http://bugs.python.org/issue11849 to Python 2.7 (Make it more likely for the system allocator to release free()d memory arenas on glibc-based systems).

Benjamin Yolken added the comment: Ahh, didn't see the "better resolution" patch later in the issue. I've updated the Python 2.7 patch here accordingly. -- Added file: http://bugs.python.org/file33894/memory_fix_updated2.patch __

[issue20494] Backport of http://bugs.python.org/issue11849 to Python 2.7 (Make it more likely for the system allocator to release free()d memory arenas on glibc-based systems).

Changes by Benjamin Yolken : Removed file: http://bugs.python.org/file33881/memory_fix.patch ___ Python tracker <http://bugs.python.org/issue20494> ___ ___ Python-bug

[issue20494] Backport of http://bugs.python.org/issue11849 to Python 2.7 (Make it more likely for the system allocator to release free()d memory arenas on glibc-based systems).

Benjamin Yolken added the comment: Attaching an updated version of the patch generated with autoconf 2.69 instead of 2.68. -- Added file: http://bugs.python.org/file33883/memory_fix_updated.patch ___ Python tracker <http://bugs.python.

[issue20494] Backport of http://bugs.python.org/issue11849 to Python 2.7 (Make it more likely for the system allocator to release free()d memory arenas on glibc-based systems).

New submission from Benjamin Yolken: We have found that http://bugs.python.org/issue11849 affects a number of our Python 2.7 systems in production. I took the changes in http://hg.python.org/cpython/rev/f8a697bc3ca8 and backported them to the head of the python 2.7 cpython hg branch. I have