[issue11849] glibc allocator doesn't release all free()ed memory
STINNER Victor
report at bugs.python.org
Sat Nov 9 05:05:25 CET 2013
STINNER Victor added the comment:
I just found this issue from this article:
http://python.dzone.com/articles/diagnosing-memory-leaks-python
Great job! Using mmap() for arenas is the best solution for this issue. I did something similar on a completly different project (also using its own dedicated memory allocator) for workaround the fragmentation of the heap memory.
----------
nosy: +haypo
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11849>
_______________________________________
More information about the Python-bugs-list
mailing list