Message 202458 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	dmalcolm, eli.bendersky, flox, kaifeng, neologix, pitrou, python-dev, vstinner
Date	2013-11-09.04:05:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1383969924.99.0.130232989435.issue11849@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2013-11-09 04:05:25	vstinner	set	recipients: + vstinner, pitrou, eli.bendersky, flox, dmalcolm, neologix, python-dev, kaifeng
2013-11-09 04:05:24	vstinner	set	messageid: <1383969924.99.0.130232989435.issue11849@psf.upfronthosting.co.za>
2013-11-09 04:05:24	vstinner	link	issue11849 messages
2013-11-09 04:05:24	vstinner	create