On Wed, 29 Apr 2009, Joshua Kwan wrote:

> I'm having a weird 100% CPU problem using the curl_multi_socket API and a
> glib main loop (driving a GTK+ UI.) When downloading a file, no matter how
> long it takes, the main loop just spams the progress callback over and over
> again (downloading a 95MB file off the local network incurs 3.6 million
> callbacks!!) Not only is this bad of its own right, but the callback happens
> so often that the UI is totally blocked while this is going on.

Hm, I wonder if there could be a bug related to the progress callback and the
multi_socket API. I don't think that combination is very widely used. The
progress callback should be more or less unnecessary in that situation I
think.

If you can produce an example that repeats this it'll be great!

-- 
  / daniel.haxx.se