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
Out of memory errors are being thrown from libcurl, when request URL ⪆ 1MB and libcurl ≥ 7.71.0. Could be a breaking API change in curl?
Or it could be a bug, athough that seems less likely. I couldn't find any open "out of memory" issues in curl, but I did find this old issue which may be relevant: curl/curl/issues/6681.
Known breaking environments
I've been able to reproduce this behaviour in:
OS
R
{curl}
libcurl
Windows 10
4.3.1
5.1.0
8.3.0
Windows 11
4.2.2
5.1.0
7.84.0
Ubuntu 2204 (AWS)
4.3.1
5.1.0
7.81.0
Ubuntu 2204 (Desktop)
4.3.1
5.1.0
7.71.0, 7.81.0, 8.4.0 (see reprex below)
Reprex
I've run the same test -- make a dumb request with a url 1MB in size -- with 4 versions of libcurl and latest {curl} R package. I've built 7.70.0, 7.71.0 and 8.4.0 from source; 7.81.0 is the default libcurl on my test environment.
My 7.70.0 reprex is the only environment that successfully sent a request (with a 4xx response, which is expected).
The URL in the reprex is large because of the querystring. Problem still occurs if scheme + authority + path ⪆ 1MB. http / https is also immaterial. curl_interrupt = TRUE/FALSE is also immaterial.
The largest url that succeeds in all environments was 1048443 bytes.
Out of memory errors are being thrown from libcurl, when request URL ⪆ 1MB and libcurl ≥ 7.71.0. Could be a breaking API change in curl?
Or it could be a bug, athough that seems less likely. I couldn't find any open "out of memory" issues in curl, but I did find this old issue which may be relevant: curl/curl/issues/6681.
Known breaking environments
I've been able to reproduce this behaviour in:
Reprex
I've run the same test -- make a dumb request with a url 1MB in size -- with 4 versions of libcurl and latest {curl} R package. I've built 7.70.0, 7.71.0 and 8.4.0 from source; 7.81.0 is the default libcurl on my test environment.
My 7.70.0 reprex is the only environment that successfully sent a request (with a 4xx response, which is expected).
The URL in the reprex is large because of the querystring. Problem still occurs if scheme + authority + path ⪆ 1MB. http / https is also immaterial.
curl_interrupt = TRUE/FALSE
is also immaterial.The largest url that succeeds in all environments was 1048443 bytes.
7.70.0
Created on 2023-11-04 with reprex v2.0.2
7.71.0
Created on 2023-11-04 with reprex v2.0.2
7.81.0
Created on 2023-11-04 with reprex v2.0.2
8.4.0
Created on 2023-11-04 with reprex v2.0.2
The text was updated successfully, but these errors were encountered: