memory leak in Python 2.1/FreeBSD? [was Re: Garbage collection on strike?]

Aahz Maruch aahz at panix.com
Thu May 17 07:07:14 EDT 2001


In article <Pine.LNX.4.33.0105170003030.912-100000 at C800000-A.potlnd1.or.home.com>,
greg jorgensen  <greg at C800000-A.potlnd1.or.home.com> wrote:
>On 10 May 2001, Aahz Maruch wrote:
>>
>> * Much more likely, though, is that you're simply not deleting object
>> references.  Garbage collection in Python only works on circular
>> references, where two or more objects refer to each other, but none has
>> any external references pointing in.  If you've got a dict, for example,
>> that has a reference to the objects that aren't disappearing, your
>> memory usage will keep going up as you allocate new objects.
>
>When you wrote "GC in Python only works on circular references" you are
>referring to the garbage collector and not the reference counting
>mechanism, right? 

Robin's given you a potential answer to your actual problem; the answer
to the question above is "yes".
-- 
                      --- Aahz  <*>  (Copyright 2001 by aahz at pobox.com)

Androgynous poly kinky vanilla queer het Pythonista   http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6

"It's such a fine line between stupid and clever."  --David St. Hubbins



More information about the Python-list mailing list