[issue10156] Memory leak (r70459)
report at bugs.python.org
Thu Oct 21 00:47:17 CEST 2010
Stefan Krah <stefan-usenet at bytereef.org> added the comment:
Marc-Andre Lemburg <report at 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 free the
> interned Unicode strings or not all of them ?
No, Valgrind's "definitely lost" category means that all pointers
to an allocated region have been lost, so it would not be possible
to free the area. 
There are hundreds of "possibly lost" warnings as well, but I did
not report those.
My experience is that Valgrind is usually correct with "definitely
lost", see e.g. #10153. That said, of course it _could_ be a false
 Last category from:
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list