Heiko Wundram wrote: > Am Donnerstag 11 Mai 2006 15:15 schrieb [EMAIL PROTECTED]: > > I MUST find a system which deallocate memory... > > Otherwise, my application crashes not hardly it's arrived to > > break-point system > > As was said before: as long as you keep a reference to an object, the object's > storage _will not be_ reused by Python for any other objects (which is > sensible, or would you like your object to be overwritten by other objects > before you're done with them?). Besides, even if Python did free the memory > that was used, the operating system wouldn't pick it up (in the general case) > anyway (because of fragmentation issues), so Python keeping the memory in an > internal free-list for new objects is a sensible choice the Python developers > took here.
BTW python 2.5 now returns free memory to OS, but if a program keeps allocating more memory with each new iteration in python 2.4, it will not help. -- http://mail.python.org/mailman/listinfo/python-list