Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #78662 > unrolled thread

Re: "High water" Memory fragmentation still a thing?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: "High water" Memory fragmentation still a thing? Antoine Pitrou <antoine@python.org> - 2014-10-03 19:16 +0000

#78662 — Re: "High water" Memory fragmentation still a thing?

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.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web