On 08/01/2014 10:44 AM, William Ehlhardt wrote: > On Fri, Aug 1, 2014 at 3:39 AM, Saúl Ibarra Corretgé <[email protected]> wrote: >> Well, your timer was called when uv_run started its process, because due >> timers are the first thing to be calculated. If you schedule more timers >> in other callbacks, they will run on the next iteration. >> >> If you think you've found an inconsistency, can you provide a test case? > > Sure. I posted this before, but here it is again (with UV_RUN_NOWAIT > instead, just for grins). Expected behavior: UV_RUN_NOWAIT should > return instead of busylooping until the end of time. See attached. >
Sorry, I must have missed it. Looks like a granularity problem. Basically, the logic in uv__run_timers will spin forever unless there is a timer due in the future. Please open an issue on GH and attach your test case. Extra points if you come up with a fix :-) -- Saúl Ibarra Corretgé bettercallsaghul.com
signature.asc
Description: OpenPGP digital signature
