On Wednesday, November 26, 2014 11:46:54 AM UTC-8, [email protected] wrote: > > I stopped it when about 5 GB of memory was used (as seen be top on that > python process). So yes, there is a leak somewhere. >
Quite probably. In principle, though, we're making such a mess of the memory that we could make python leak even without direct leaks: Some of our data structures need *repeated* gc calls to clean all garbage (because cleaning a cyclic garbage cluster might cause another part to become cyclic garbage, which will only be collected with the next gc call). Python doesn't do repeated gc's. So I strongly suspect we could engineer an example where our rate of garbage production exceeds the rate at which gc recovers it. -- 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.
