On Wed, 10 Sep 2025, Stephane Cruchon via curl-library wrote:
We've observed a situation where curl_timediff_us() seems to spin in a tight loop when libcurl runs inside a container. This leads to high cpu usage.
What happened that took libcurl to this state? What is curl doing when this happens?
curl_timediff_us() itself does not get stuck and in the follow up email you indicated that it might be related to the splay tree management.
We fixed a splay related issue recently, so maybe the latest version works better for you.
I doubt it is actually related to the time. -- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
