➜

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 christian.heimes
Recipients christian.heimes, gvanrossum, janssen
Date 2007-12-06.14:06:51
SpamBayes Score 0.05445342
Marked as misclassified No
Message-id <1196950013.15.0.53021652857.issue1469@psf.upfronthosting.co.za>
In-reply-to
Content 
I can reproduce the problem when I run the ssl tests with -unetwork.

I've used PYTHONDUMREFS and combinerefs.py to find the leaking objects.
I'm seeing lots of

0x9fd3e4c [1] SSLSocket
0x9fd2928 [1] ssl.SSLContext <ssl.SSLContext object at 0x9fd2928>
0x9fd5b74 [1] dict {'certfile': None, '_sslobj': <ssl.SSLContext object
at 0x9fd2928>, 'do_handshake_on_con
nect': True, 'ssl_version': 1, '_base': None, 'cert_reqs': 2,
'ca_certs': '/home/heimes/dev/python/py3k/Lib
/test/https_svn_python_org_root.pem', 'keyfile': None,
'suppress_ragged_eofs': True}

in the output.

I guess the problem is connected to::

    _ssl.sslwrap(self, server_side,
        keyfile, certfile,
        cert_reqs, ssl_version, ca_certs)

in Lib/ssl.py. I'm digging in
History
Date User Action Args
2007-12-06 14:06:53christian.heimessetspambayes_score: 0.0544534 -> 0.05445342
recipients: + christian.heimes, gvanrossum, janssen
2007-12-06 14:06:53christian.heimessetspambayes_score: 0.0544534 -> 0.0544534
messageid: <1196950013.15.0.53021652857.issue1469@psf.upfronthosting.co.za>
2007-12-06 14:06:53christian.heimeslinkissue1469 messages
2007-12-06 14:06:52christian.heimescreate