"High water" Memory fragmentation still a thing?
antoine at python.org
Fri Oct 3 21:16:57 CEST 2014
Croepha <croepha <at> gmail.com> writes:
> Does python in general terms (apart from extensions or gc manipulation),
exhibit a "high water" type leak of allocated memory in recent python
It is not a leak. It is a quite common pattern of memory fragmentation.
The article is wrong in assuming that Python doesn't return the memory to
the OS. Python does return its empty memory pools to the OS, however the OS
itself may not be able to release that memory, because of heap fragmentation.
As the article mentions, this was improved (mostly fixed?) in 3.3.
More information about the Python-list