[issue12075] python3.2 memory leak when setting integer key in dictionary

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12075] python3.2 memory leak when setting integer key in dictionary

kai zhu added the comment: explicit gc.collect() doesn't seem to fix the leak in my application. my current fix is to not re-instantiate the class attribute (which cost ~7mb) during reload & instead reference one created earlier. i haven't pinpointed y, but i suspect its a corner case, which w

[issue12075] python3.2 memory leak when setting integer key in dictionary

Amaury Forgeot d'Arc added the comment: It's simply because all classes form a cycle (Foo -> Foo.__mro__ -> Foo) A class and class attributes can only be freed with gc.collect(). Did you disable the garbage collector? -- nosy: +amaury.forgeotdarc ___

[issue12075] python3.2 memory leak when setting integer key in dictionary

Ezio Melotti added the comment: I think this has to do with class attributes and reload(): wolf@hp:~/dev/py/py3k$ cat leak.py class Foo: pass Foo.l = list(range(65535)) wolf@hp:~/dev/py/py3k$ ./python Python 3.3a0 (default:4b122cac7ac5+, May 14 2011, 10:01:13) [GCC 4.5.2] on linux2 Type "hel

[issue12075] python3.2 memory leak when setting integer key in dictionary

New submission from kai zhu : i'm using the latest debian unstable python3.2 build on colinux (2011, may, 14) ## leak.py ## >>> import imp, leak; imp.reload(leak) ## will leak ~2.5mb per reload ## on i386 debian unstable machine (according to top). ## in my real world app (an automatic build sys