I'm still not sure what the problem is.  This code was working fine when I committed it, no leaks, so something else must have changed under the covers.  I don't believe that adding GC to the C code is the answer; it should be automatically GC'd.  So I'd back that patch out.

I intend to wolf-fence the tests in the test module until I find a single test that causes the leaks.  Sorry I haven't had time to look at this earlier, but we're in the middle of a big presentation afternoon here at work.

On Dec 6, 2007 11:45 AM, Christian Heimes <report@bugs.python.org> wrote:

Christian Heimes added the comment:

Guido van Rossum wrote:
> I just reverted it. I put a bit of debugging in the call to
> _real_close(), and even with Christian's corrections it fails miserably.
> I prefer leaking.

I agree! I've not enough time to work on the patch. A working patch
requires some redesign of the ssl interface. It's definitely too late now.

Christian

__________________________________
Tracker <report@bugs.python.org>
< http://bugs.python.org/issue1469>
__________________________________