Robert Bradshaw wrote: > On Feb 20, 2009, at 10:56 PM, Michael Abshoff wrote:
Hi Robert, >>> I found and fixed two memory leaks. >> Got a patch for me? I could still get that one into 3.3 :) > > Memory leaks in Cython, not in Sage. (Actually, probably not > noticeable ones, one was leaking an exception, and the other was > "leaking" the values True and False in most cases. Well, we had 8 byte leaks in Sage that ate up all available RAM on the old sage.math in about two or three days, i.e. leaking about 1 to 2 GB/hour, so if you hit them often enough even tiny leaks have a giant impact. And I have some cases where I do hope that the refnanny will point out ref count issues and explain leaks where I have been totally unable to pin point a cause in Sage code itself. Getting Sage to start up and exit clean will be great, but the test suite will likely expose many more issues :) <SNIP> > I'm going to run it overnight. Given that Sage doesn't exit cleanly > (not sure what's up with that), I expect everything to fail, but > hopefully it'll still be useful. Sure. I took today's cython spkg and I am valgrinding Sage with it, so maybe I can give you some pointer what is going wrong. > - Robert Cheers, Michael > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
