Stefan Krah stefan-use...@bytereef.org added the comment:
Re disabling interning in PyDict_SetItemString:
A comment in unicodeobject.c says that globals should not be used
before calling _PyUnicode_Init. But in Py_InitializeEx (pythonrun.c)
_PyUnicode_Init is called after _Py_ReadyTypes,
New submission from Stefan Krah stefan-use...@bytereef.org:
This is one of two remaining definitely lost leaks in py3k. It started
to appear in r70459. How to reproduce:
make distclean ./configure OPT=-O0 -g --without-pymalloc make
valgrind --leak-check=full
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10156
___
___
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
The stack corresponds to the allocation of type(sys.float_info).__doc__.
Why would only this object appear as a memory leak? It is certainly not
deallocated, but all other types are in the same situation.
For example, sys.int_info is
Stefan Krah stefan-use...@bytereef.org added the comment:
To add to the mystery, the leak disappears if the key value is not
interned in PyDict_SetItemString:
Index: Objects/dictobject.c
===
--- Objects/dictobject.c
Marc-Andre Lemburg m...@egenix.com added the comment:
Stefan Krah wrote:
Stefan Krah stefan-use...@bytereef.org added the comment:
To add to the mystery, the leak disappears if the key value is not
interned in PyDict_SetItemString:
I'm not sure how you determine what is a leak and what
Stefan Krah stefan-use...@bytereef.org added the comment:
Marc-Andre Lemburg rep...@bugs.python.org wrote:
I'm not sure how you determine what is a leak and what not.
Interned Unicode objects stay alive until the interpreter
is finalized.
Are you suggesting that the finalization does not
