Dear Simon, you are right, and I was wrong in claiming that collect() relieves matters. Just found out that the call of collect() tremendously slows down the program. So it would take quite long until it reaches the stage where the version without collect() needed only a few minutes to consume 6 GB of memory.
Best wishes, Peter Am Dienstag, 11. November 2014 18:27:53 UTC+1 schrieb Simon King: > > Hi Peter, > > On 2014-11-11, Peter Mueller <[email protected] <javascript:>> wrote: > > A tentative solution seems to be to put a `collect()' inside the loop > (and > > a `from gc import collect' at the beginning of the program). Still, I > > believe that this issue deserves attention. > > If gc.collect() solves the issue, then I suppose it is not a memory leak > after all. Unless you explicitly disable it, Python cyclic garbage > collector will occasionally do a collection anyway (though not after > each deletion of an object). > > Best regards, > Simon > > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
