Antoine Pitrou antoine at python.org
Fri Oct 3 15:16:57 EDT 2014

• Previous message (by thread): "High water" Memory fragmentation still a thing?
• Next message (by thread): "High water" Memory fragmentation still a thing?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hello,

Croepha <croepha <at> gmail.com> writes:
> 
> Question:
> 
> Does python in general terms (apart from extensions or gc manipulation),
exhibit a "high water" type leak of allocated memory in recent python
versions (2.7+)?

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.

Regards

Antoine.

---

• Previous message (by thread): "High water" Memory fragmentation still a thing?
• Next message (by thread): "High water" Memory fragmentation still a thing?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list