[issue1469] SSL tests leak memory

[Bill Janssen]

Bill Janssen added the comment:

The server isn't handling the close event properly.  I'll fix that.

On Dec 13, 2007 9:06 PM, Guido van Rossum <report at bugs.python.org> wrote:

>
> Guido van Rossum added the comment:
>
> I spoke too soon. In a debug build, this hangs forever during the
> second iteration:
>
> ./python.exe Lib/test/regrtest.py -uall -R1:1 test_ssl
>
> Adding -v, it looks like two iterations are carried out perfectly (one
> must be a trial run, one the warm-up run), but the third run goes
> beserk; the output ends like this:
>
> testAsyncoreServer (test.test_ssl.ThreadedTests) ...
>  server:  read b'over\n' from client
>  server:  closed connection <ssl.SSLSocket object, fd=6, family=2,
> type=1, proto=0>
>  server:  read b'' from client
>  server:  closed connection <ssl.SSLSocket object, fd=10, family=2,
> type=1, proto=0>
>  server:  read b'' from client
>  server:  closed connection <ssl.SSLSocket object, fd=10, family=2,
> type=1, proto=0>
> .
> . (the last two lines repeated forever)
> .
>
> __________________________________
> Tracker <report at bugs.python.org>
> <http://bugs.python.org/issue1469>
> __________________________________
>

Added file: http://bugs.python.org/file8954/unnamed

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1469>
__________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: unnamed
Url: http://mail.python.org/pipermail/python-bugs-list/attachments/20071214/dab6e75c/attachment-0001.txt