Re: [Python-Dev] Mixing memory management APIs
"M.-A. Lemburg"
Neal Norwitz wrote:
"M.-A. Lemburg" wrote:
I've checked in a patch for the UTF-8 codec problem. Could you try Purify against the CVS version ?
with-pymalloc or without or both?
Both if possible -- the leakage showed up with pymalloc AFAIR :-)
I thought we were chasing memory stomping, not leaking, this time around... Cheers, M. -- /* I'd just like to take this moment to point out that C has all the expressive power of two dixie cups and a string. */ -- Jamie Zawinski from the xkeycaps source
Michael Hudson wrote:
I've checked in a patch for the UTF-8 codec problem. Could you try Purify against the CVS version ?
with-pymalloc or without or both?
Both if possible -- the leakage showed up with pymalloc AFAIR :-)
I thought we were chasing memory stomping, not leaking, this time around...
Both, I guess: pymalloc doesn't behave well with overallocation and codecs use this technique a lot. I reduced the overallocation in the UTF-8 encoder down from 3*size to 2*size which should cover the most common cases better than before. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
participants (2)
-
M.-A. Lemburg -
Michael Hudson