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 sYnfo
Recipients sYnfo
Date 2013-09-03.11:46:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378208801.81.0.941164435803.issue18913@psf.upfronthosting.co.za>
In-reply-to
Content
Doing 'valgrind --suppressions=Misc/valgrind-python.supp ./python Lib/tests/test_ssl.py' I'm getting:

==322== LEAK SUMMARY:
==322==    definitely lost: 32 bytes in 1 blocks
==322==    indirectly lost: 392 bytes in 16 blocks
==322==      possibly lost: 1,617,191 bytes in 1,052 blocks
==322==    still reachable: 4,068,239 bytes in 3,201 blocks
==322==         suppressed: 0 bytes in 0 blocks


I managed to reduce that to a shorter reproducer:

"""
import os
import ssl

NULLBYTECERT = os.path.join(os.path.dirname(__file__) or os.curdir, "nullbytecert.pem")
p = ssl._ssl._test_decode_cert(NULLBYTECERT)
"""

where NULLBYTECERT is the cert introduced in issue18709.

Python 2.7 does not leak like this, and the PySSL_test_decode_certificate function looks the same there as in Python 2.6, so I assume it's something else that does the actual leaking.
History
Date User Action Args
2013-09-03 11:46:41sYnfosetrecipients: + sYnfo
2013-09-03 11:46:41sYnfosetmessageid: <1378208801.81.0.941164435803.issue18913@psf.upfronthosting.co.za>
2013-09-03 11:46:41sYnfolinkissue18913 messages
2013-09-03 11:46:41sYnfocreate