Re: Memory Leaks and Heapy

2008-01-07 Thread Yaakov Nemoy
On Jan 7, 2008 7:55 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > Fair enough. Just wanted to give some more details as to > where to look for things that look like leaks, but are in > fact just results of internal feature of the Python > interpreter. We have a hackfest coming up in the Fedora Co

Re: Memory Leaks and Heapy

2008-01-07 Thread M.-A. Lemburg
On 2008-01-05 03:19, Yaakov Nemoy wrote: > On Jan 4, 2008 11:56 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >>> The most common answer I heard was possible fragmentation, meaning >>> there are no or few completely empty blocks to be found. If there are >>> no 'leaks' in the VM, then it's probably

Re: Memory Leaks and Heapy

2008-01-05 Thread Andrew MacIntyre
Yaakov Nemoy wrote: > 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? Marc-Andre bro

Re: Memory Leaks and Heapy

2008-01-04 Thread Yaakov Nemoy
On Jan 4, 2008 11:56 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > > The most common answer I heard was possible fragmentation, meaning > > there are no or few completely empty blocks to be found. If there are > > no 'leaks' in the VM, then it's probably related to how memory is > > freed. > > Yo

Re: Memory Leaks and Heapy

2008-01-04 Thread M.-A. Lemburg
On 2008-01-04 17:23, Yaakov Nemoy wrote: > On Jan 4, 2008 11:10 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >> If you're using lots of small objects, you may be running into a >> problem with the Python memory allocation mechanism, pymalloc. It used >> to not return memory to the system. In Python

Re: Memory Leaks and Heapy

2008-01-04 Thread Christian Heimes
Jeroen Ruigrok van der Werven wrote: > 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 w

Re: Memory Leaks and Heapy

2008-01-04 Thread Yaakov Nemoy
On Jan 4, 2008 11:10 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > If you're using lots of small objects, you may be running into a > problem with the Python memory allocation mechanism, pymalloc. It used > to not return memory to the system. In Python 2.5 (IIRC, could be > 2.6) this was changed t

Re: Memory Leaks and Heapy

2008-01-04 Thread Yaakov Nemoy
On Jan 4, 2008 10:34 AM, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > As various people pointed out to me: > http://wingolog.org/archives/2007/11/27/reducing-the-footprint-of-python-applications It did; it's what lead me to Heapy. > Aside from that (rant), I seriously dislike Python

Re: Memory Leaks and Heapy

2008-01-04 Thread M.-A. Lemburg
On 2008-01-04 16:07, Yaakov Nemoy wrote: > Hi list, > > Firstly, this is my first post here, so I hope I'm not breaking some > unwritten etiquette rule about asking questions involving several > different libraries. > > I'm trying to plug some memory leaks in a TurboGears program. We (the > Fedo

Re: Memory Leaks and Heapy

2008-01-04 Thread Jeroen Ruigrok van der Werven
-On [20080104 16:11], Yaakov Nemoy ([EMAIL PROTECTED]) 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