You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is reproducible with the hiperfifo, evhiperfifo and multi-uv examples.
With the multi-uv example, start: multi-uv https://curltest.szalonna.org/testfiles/128K
Or with the hiperfifo example, start: hiperfifo &; sleep 1; echo https://curltest.szalonna.org/testfiles/128K > hiper.fifo
With version 7.54.1 and earlier this downloaded the file successfully.
From 7.55.0 the downloads are interrupted or hanging depending on which example you use.
This happens if the latency is around or higher than 200ms.
The curltest.szalonna.org test server has artificially high latency for testing purposes.
Git bisect showed that #1547 caused the regression.
I have only tested it on Linux, but I think other operating systems are affected as well.
I have a one-line patch to solve this, I will create a pull request.
The text was updated successfully, but these errors were encountered:
I'm not quite sure why this patch fixes the issue, but I could trace it to that line and conn->connectstate was NULL there. The current operation exited but since no timeouts nor socket polls are left, curl is never called again.
This issue is reproducible with the hiperfifo, evhiperfifo and multi-uv examples.
With the multi-uv example, start:
multi-uv https://curltest.szalonna.org/testfiles/128K
Or with the hiperfifo example, start:
hiperfifo &; sleep 1; echo https://curltest.szalonna.org/testfiles/128K > hiper.fifo
With version 7.54.1 and earlier this downloaded the file successfully.
From 7.55.0 the downloads are interrupted or hanging depending on which example you use.
This happens if the latency is around or higher than 200ms.
The
curltest.szalonna.org
test server has artificially high latency for testing purposes.Git bisect showed that #1547 caused the regression.
I have only tested it on Linux, but I think other operating systems are affected as well.
I have a one-line patch to solve this, I will create a pull request.
The text was updated successfully, but these errors were encountered: