On Jan 8, 2009, at 5:11 PM, Michael Abshoff wrote: > If someone fixes this I will get right back to testing. I will see > what > is going on, maybe this is fixable for me in which case it should be > trivial :)
I think a lot of this kind of error is rather trivial, it's just that no one handled a certain case for new-style temps. I've just had too many other higher-priority things to do to attack this. >> >> As a regression tool, I would be happy if the memory increase >> remained the same with the old and new Cython (or, e.g., between runs >> of Sage). At least it could probably pinpoint egregious issues. I bet >> twice is enough for 90+% of the code out there. >> > > Well, the main issue for me here is to hunt down the small root causes > if leaks since I can find plenty of large scope examples that go nuts. > But all the low hanging fruits in the C heap, i.e. sparse linear > algebra > have been fixed, so now the issues are also with Cython/Python and I > don't know enough about this yet to make headway on my own. Obviously > that ought to change over time, especially when I get some nice tools > like the reference count nanny. I think Cython 0.10 was pretty tight (perhaps not completely bug free, but mostly). I think 0.11 hasn't even been tested enough yet. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
