Bugs item #1603712, was opened at 2006-11-27 19:28
Message generated for change (Comment added) made by victor_snezhko
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1603712&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: compile or build problem
Group: bad behaviour
Status: Closed
Resolution: Later
Priority: 5
Private: No
Submitted By: Sebastien WILLEMIJNS (sebone)
Assigned to: Daniel Stenberg (bagder)
Summary: curl 7.16-0 now use "limit rate" badly

Initial Comment:
http://80.247.230.136/bug/curl7160-bug-in-limit-rate.bmp

When i use "--limit-rate" in 7-16.0 this function crash/stops software when speed is equal or is more value i choose

========> choose 5K as value and software stops, choose 5000M and software do not stop !!! <========

bug are not been detected in 7.15.5 because the package is not present in curl archive packs ;)

my config XP SP2 100% patched French version
versions are both nossl

----------------------------------------------------------------------

Comment By: vvs (victor_snezhko)
Date: 2007-01-01 22:01

Message:
Logged In: YES
user_id=1680849
Originator: NO

I also experience this problem.
After some debugging, I see that there is a loop in Transfer(), the first
pass of which works fine. On the second pass Curl_select() is called with
fd_read == fd_write == -1.
It returns ENOENT (errno == 2), and the whole transfer stops.

BTW, in this case Transfer() returns CURLE_OK, and error doesn't propagate
to caller...

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-12-19 15:01

Message:
Logged In: YES
user_id=1110
Originator: NO

Follow-up from the curl-users mailing list discussion: this clearly breaks
the connection on Windows when the rate limiting logic is used (i.e if you
set the limit to way over your bandwidth there's no problem seen). This
does however seem to work fine on Linux.

Someone with a debugger (or similar) on windows would need to set a few
breakpoints and single-step over a few functions to see what happens and
why. I don't have any such and I'll therefore mark this bug "later", close
it and add it to the KNOWN_BUGS document - since nobody has stepped forward
offering to do what needs to be done.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-12-10 18:47

Message:
Logged In: YES
user_id=1110
Originator: NO

re-opened since Sebastien still experience connection closes

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-12-06 22:47

Message:
Logged In: NO

please reopen this bug :-(

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-12-05 20:42

Message:
Logged In: YES
user_id=1110
Originator: NO

I fixed the limit-rate problem that made it not limiting the rate
properly, but I have not seen nor addressed any crashs/stops.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-11-28 14:05

Message:
Logged In: YES
user_id=1110
Originator: NO

(for the sake of keeping info in this report as well) --limit-rate is
indeed broken in 7.16.0, but I have not found any reasons for the aborted
transfers:

http://curl.haxx.se/mail/archive-2006-11/0135.html

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1603712&group_id=976
Received on 2007-01-01