Memory Leaks and Heapy

[Jeroen Ruigrok van der Werven]

-On [20080104 16:11], Yaakov Nemoy (loupgaroublond at gmail.com) wrote:
>I'm trying to plug some memory leaks in a TurboGears program.  We (the
>Fedora Project) have a few apps in Turbogears in infrastructure that
>all seem to be running into the same issues in a variety of
>configurations.  Hopefully when I get to the cause of this in one app,
>Smolt, we can fix the others too.

[snip]

>A couple of developers have mentioned that python might be fragmenting
>its memory space, and is unable to free up those pages.  How can I go
>about testing for this, and are there any known problems like this?
>If not, what else can I do to look for leaks?

As various people pointed out to me:
http://wingolog.org/archives/2007/11/27/reducing-the-footprint-of-python-applications

That might help.

Aside from that (rant), I seriously dislike Python's memory management and
even more the fairly arcane ways people have to go about
debugging/troubleshooting some 600 MB to 2-3 GB(!) of resident memory use by
Python.

Personally I consider this the weakest point of Python. Given the fact there
is a garbage collector this sort of keeping track of memory seems a bit
contradictory to the concept of garbage collection.

(And yes, I am investigating this and also how to get it leaner and better.)

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
Speak the sweet truth...