Message 205624 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	rstarostecki, skrah, vstinner
Date	2013-12-09.00:30:50
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1386549050.75.0.868448254943.issue19893@psf.upfronthosting.co.za>
In-reply-to

Content
Sorry, but I still don't understand this issue. "Invalid read of size 4" is a known false positive. It can be worked around using ./configure --with-valgrind and the suppression list, or using ./configure --without-pymalloc. If you still get the warning, you used the wrong options or you are still using another Python binary (or shared library). Make sure that you are linked to your newly compiled shared library. "valgrind --leak-check=full --log-file=valgrind.log ./python -c pass" shows me "possibly lost: 286,779 bytes in 654 blocks". This is also another known issue: Python doesn't release all the memory at exit, they are many "singletons" and variables initialized once but never released. The PEP 3121 helps this issue but the PEP is not fully implemented yet, many modules should still be modified. So what is your question? Do you think that Python leaks memory? Why do you think so?

Sorry, but I still don't understand this issue.

"Invalid read of size 4" is a known false positive. It can be worked around using ./configure --with-valgrind and the suppression list, or using ./configure --without-pymalloc. If you still get the warning, you used the wrong options or you are still using another Python binary (or shared library). Make sure that you are linked to your newly compiled shared library.

"valgrind --leak-check=full --log-file=valgrind.log ./python -c pass" shows me "possibly lost: 286,779 bytes in 654 blocks". This is also another known issue: Python doesn't release all the memory at exit, they are many "singletons" and variables initialized once but never released.

The PEP 3121 helps this issue but the PEP is not fully implemented yet, many modules should still be modified.

So what is your question? Do you think that Python leaks memory? Why do you think so?

History
Date	User	Action	Args
2013-12-09 00:30:50	vstinner	set	recipients: + vstinner, skrah, rstarostecki
2013-12-09 00:30:50	vstinner	set	messageid: <1386549050.75.0.868448254943.issue19893@psf.upfronthosting.co.za>
2013-12-09 00:30:50	vstinner	link	issue19893 messages
2013-12-09 00:30:50	vstinner	create