mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-05-10 17:12:41 +02:00
handle_connect_state (used by <link rel=preconnect>) attached easy handles to the multi without setting CURLOPT_RESOLVE, so libcurl spawned its own threaded resolver for them. When the system stub resolver was slow, the thread got stuck and the next ~Request pthread_join'd it on the main thread for many seconds. Route Connect-mode requests through the same DNS + CURLOPT_RESOLVE path that Fetch uses, so libcurl never spawns the thread.