test_all goes into endless loop (memory leak)

[GoogleCodeExporter]

1. build serf 0.7.2 with Visual Studio (using serf.mak) under Windows 7 (x64)
2. run nmake CHECK -f serf.mak

test_all just goes into an endless loop (reserving more and more memory) inside 
the test_serf_closed_connection's while(1) loop. It reserves up to 2GB of 
memory on my computer and finally crashes because of system restrictions.

commenting out the call of this function in function test_context() will run 
(successfully) all other tests.

Original issue reported on code.google.com by pspend...@googlemail.com on 22 May 2011 at 10:55

[GoogleCodeExporter]

Would it be possible to please check with Serf trunk?

I don't have a Windows build environment, but a number of memory fixes have 
been recently committed to trunk that I think may resolve this issue.

(test_all runs fine here on Mac OS X.)

Original comment by justin.e...@gmail.com on 25 May 2011 at 1:13

[GoogleCodeExporter]

No, just checked with trunk, doesn't improve at all. still the same issue.

Original comment by pspend...@googlemail.com on 25 May 2011 at 2:03

[GoogleCodeExporter]

Yah, this is due to WSAPoll() implementation in APR 1.4.x being buggy.  (This 
is also affecting non-blocking connect() calls when there is no server on the 
other end.)

This patch works here in my Win7 / VS2008SP1 build environment.  I'd appreciate 
if you can confirm.

Original comment by justin.e...@gmail.com on 27 May 2011 at 7:04

• Changed state: Accepted

Attachments:

• select-poll.patch

[GoogleCodeExporter]

Original comment by justin.e...@gmail.com on 27 May 2011 at 7:05

• Added labels: OpSys-Windows

[GoogleCodeExporter]

Yes, that fixes the issue...
Could you possibly backport that fix too? Thanks a lot.

Original comment by pspend...@googlemail.com on 30 May 2011 at 8:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The fix is now committed, in r1643.

Original comment by lieven.govaerts@gmail.com on 13 Sep 2012 at 8:15