"Help needed - I don't understand how Python manages memory"

Torsten Bronger bronger at physik.rwth-aachen.de
Sun Apr 20 20:02:37 CEST 2008


Hallöchen!

Gabriel Genellina writes:

> En Sun, 20 Apr 2008 14:43:17 -0300, Christian Heimes <lists at cheimes.de>
> escribió:
>
>> Gabriel Genellina schrieb:
>>
>>> Apart from what everyone has already said, consider that
>>> FreqDist may import other modules, store global state, create
>>> other objects... whatever.  Pure python code should not have any
>>> memory leaks (if there are, it's a bug in the Python
>>> interpreter). Not-carefully-written C extensions may introduce
>>> memory problems.
>>
>> Pure Python code can cause memory leaks. No, that's not a bug in
>> the interpreter but the fault of the developer. For example code
>> that messes around with stack frames and exception object can
>> cause nasty reference leaks.
>
> Ouch!
> May I assume that code that doesn't use stack frames nor stores
> references to exception objects/tracebacks is safe?

Circular referencing is no leaking on the C level but in a way it is
memory leaking, too.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                                      Jabber ID: bronger at jabber.org
               (See http://ime.webhop.org for further contact info.)



More information about the Python-list mailing list