On Fri, 1 Nov 2013, Shao, Shuchao wrote:

> I have tested that 7.28.0 and 7.28.1 work well, and 7.29.0 will occur the
> issue very soon. So the bug should be introduced from 7.29.0.

Okay great, then we're down to 260 contenders. 7.29.0 was the first release we
did after the rather large internal restructure in commit c43127414d89ccb9
(the so called "always-multi"). It wouldn't surprise me a lot if you'd find
that the bug exists after that commit but not before.

It wouldn't really tell us how to fix the problem though, as reverting that
isn't really helping. Can you verify if that commit is the one introducing the
probilem?

Further, you explained that you see the problem with 5000 connections but can
you think of an easier way to repeat the problem in a lesser scale and in a
way that we could repeat perhaps?

The connections that you see in CLOSE_WAIT wrongly, how were they supposed to
be disconnected or not if things had been done correctly?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html