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 janssen
Recipients christian.heimes, gvanrossum, janssen
Date 2007-12-10.22:05:24
SpamBayes Score 0.10201044
Marked as misclassified No
Message-id <1197324325.18.0.744332298557.issue1469@psf.upfronthosting.co.za>
In-reply-to
Content
I think I've figured it out.  My initial patch to socket.py and ssl.py
had an extra method defined on socket.socket, _real_close(), which did'
the cleanup work of deallocating the underlying socket, and in the SSL
subclass, of releasing the SSL context.  Guido must have removed that
method, and folded what it does into the socket.close() call.  But that
means that subclasses can't hook onto that code, to get cleaned up
when the socket is truly closed.  So the SSL context gets leaked.

Adding _real_close() back to the socket module fixes most of the leak,
but not all of it.  I'm looking for the other problem...
History
Date User Action Args
2007-12-10 22:05:25janssensetspambayes_score: 0.10201 -> 0.10201044
recipients: + janssen, gvanrossum, christian.heimes
2007-12-10 22:05:25janssensetspambayes_score: 0.10201 -> 0.10201
messageid: <1197324325.18.0.744332298557.issue1469@psf.upfronthosting.co.za>
2007-12-10 22:05:25janssenlinkissue1469 messages
2007-12-10 22:05:24janssencreate