Lines Matching full:busy
1074 libcurl code execution paths this could trigger busy wait loops with
2188 running on fast processors to do short bursts of busy-loops.
2195 result in (much) less busy-loop situations and thus less CPU usage with no
2318 earlier), libcurl will busy-loop in this situation when the easy interface
3479 - Stefan Krause reported a busy-looping case when using the multi interface
3480 and doing CONNECT to a proxy. The app would then busy-loop until the proxy
