Robert Bradshaw wrote: > On Jan 8, 2009, at 5:01 PM, Michael Abshoff wrote:
<SNIP> Hi Robert, >> Well, I don't get very far: >> >> AttributeError: 'CoerceToTempNode' object has no attribute 'old_temp' >> Traceback (most recent call last): > > [...] > >> line 666, in release_temp_result >> if self.old_temp: >> AttributeError: 'CoerceToTempNode' object has no attribute 'old_temp' >> >> This is head of 0.11-devel and I made sure the old Cython was removed. > > :( > 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 :) <SNIP> > > 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. >> >> And valgrind offers other fun tools like exp-omega, exp-ptrcheck >> and so >> on :) > > Yes, I was commenting on the fact that we don't worry about > performance loss in these cases. Yep, I agree 100%. > - 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
