| commit | b7f17e4bb4627a0a8bd9a4fe20e9f4e26e9a4d28 | [log] [tgz] |
|---|---|---|
| author | Amaury Forgeot d'Arc <amauryfa@gmail.com> | Thu Nov 15 20:52:21 2007 +0000 |
| committer | Amaury Forgeot d'Arc <amauryfa@gmail.com> | Thu Nov 15 20:52:21 2007 +0000 |
| tree | 5c38ca1612fe95bee26dce5af472585b33fd0a74 | |
| parent | 519a042c7c248e3ae23cf2a3c1152f91a5bd2791 [diff] |
Found another memory leak in longrangeiter. And redo the previous correction
without calling PyType_Ready().
Question 1: Should the interpreter register all types with PyType_Ready()?
Many types seem to avoid it.
Question 2: To reproduce the problem, run the following code:
def f():
while True:
for a in iter(range(0,1,10**20)):
pass
f()
And watch the memory used by the process.
How do we test this in a unittest?