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 jtaylor
Recipients StyXman, bar.harel, jtaylor, neologix, pitrou, vstinner, ztane
Date 2016-04-21.22:21:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461277291.73.0.399884519648.issue26601@psf.upfronthosting.co.za>
In-reply-to
Content
simplest way to fix this would be to not use malloc instead of mmap in the allocator, then you also get MADV_FREE for free when malloc uses it.
The rational for using mmap is kind of weak, the source just says "heap fragmentation". The usual argument for using mmap is not that but the instant return of memory to the system, quite the opposite of what the python memory pool does.
History
Date User Action Args
2016-04-21 22:21:31jtaylorsetrecipients: + jtaylor, pitrou, vstinner, StyXman, neologix, ztane, bar.harel
2016-04-21 22:21:31jtaylorsetmessageid: <1461277291.73.0.399884519648.issue26601@psf.upfronthosting.co.za>
2016-04-21 22:21:31jtaylorlinkissue26601 messages
2016-04-21 22:21:31jtaylorcreate