New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
return more memory from unicode objects to system #46574
Comments
This patch returns more memory to the system when doing: >>> x = [unicode(i) for i in xrange(1000000)] If the above code is done, the memory before and after is quite |
Hi Neal, This seems to be a more general problem than just unicode. eg. Tuples:
And user-defined objects: >>> class A(object):
... def __init__(self):
... self.x = random.random()
>>> x = [A() for i in xrange(800000)]
>>> del x Both exhibit the same behaviour. Naively to me it seems like using the |
On Mon, Mar 17, 2008 at 11:55 AM, Alec Thomas <report@bugs.python.org> wrote:
Kinda, sorta. The general issue is the pattern of memory
The memory that is not returned is in the integer free list. If this
That doesn't hold on to any extra memory. The problem is that holes
In general, we should find places (like unicode) that use PyMem_* (ie, Alec, can you find places that are using the PyMem_* interface and |
Sure thing! I'll see if I can finish it today, but if not I'll work on |
Just for the record, the enhanced profiler source files in |
Looks good, Neal. Are you hesitant to check this in? I ran a little |
After discussing this with MvL, I'll check this patch into trunk and Committed revision 61458. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: