On Thu, 5 Oct 2006, Jeff Pohlmeyer wrote:

> Yes, that seems to solve the "below-zero" problem, but it still seems like
> there is something weird going on.

Ok. I'll do that state check fix (somewhat differently) and commit.

> Sometimes the app just seems to stall, and the CURLOPT_* timeout settings
> don't have any effect. Whenever it gets in this state, libevent's event loop
> eats up 100% CPU.

When this happens, does it stall forever or just "a while" ?

> I am also sometimes getting handles that show COMPLETED in multistate, but
> aren't getting picked up as CURLMSG_DONE in my curl_multi_info_read() loop.

I believe you can fix this bug in hiperfifo.c like this:

--- hiperfifo.c 2006-10-07 22:50:02.000000000 +0200
+++ debugit.c 2006-10-07 22:53:32.000000000 +0200
@@ -154,6 +154,7 @@
          if (msg->msg == CURLMSG_DONE) {
            easy=msg->easy_handle;
            res=msg->data.result;
+ break;
          }
        }
        if (easy) {

... at least it seems to fix it for me.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html