luo980/curl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

KNOWN_BUGS: remove "Multi perform hangs waiting for threaded resolver"

Browse Source 
We now offer a way to avoid that hang, using CURLOPT_QUICK_EXIT.

Follow-up to 49798cac83 fixed via #9147

Closes #9999
This commit is contained in:
Daniel Stenberg 2022-11-29 14:50:23 +01:00
parent 862406c5e1
commit f85e932b28
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/KNOWN_BUGS
View File

@ -104,7 +104,6 @@ problems may have been fixed or changed somewhat since this was written.
11.9 DoH does not inherit all transfer options
11.10 Blocking socket operations in non-blocking API
11.11 A shared connection cache is not thread-safe
11.14 Multi perform hangs waiting for threaded resolver
11.15 CURLOPT_OPENSOCKETPAIRFUNCTION is missing
11.16 libcurl uses renames instead of locking for atomic operations
@ -763,15 +762,6 @@ problems may have been fixed or changed somewhat since this was written.
See https://github.com/curl/curl/issues/4915 and lib1541.c
11.14 Multi perform hangs waiting for threaded resolver
If a threaded resolver takes a long time to complete, libcurl can be blocked
waiting for it for a longer time than expected - and longer than the set
timeouts.
See https://github.com/curl/curl/issues/2975 and
https://github.com/curl/curl/issues/4852
11.15 CURLOPT_OPENSOCKETPAIRFUNCTION is missing
When libcurl creates sockets with socketpair(), those are not "exposed" in