Timer.unref()

[liveinjs]

var t = setTimeout(function(){console.log("t")}, 10);
t.unref();

and

 var t = setTimeout(function(){console.log("t")}, 1000);
t.unref();

These two code snippets to be run ,but the result is different .

[othiym23]

This is to be expected. When you unref the timer in the first case, because the timeout is so short the timer has a chance to run before the process exits. In the second, the timer is set to fire too far in the future and libuv exits the event loop (and the process) before t can be printed to the console. This is why timers aren't unreferenced by default.

[tjfontaine]

thanks for clarifying @othiym23 I was confused by what I was supposed to be seeing here.

So while he's right it's not entirely surprising, I am slightly bemused by the fact that it's happening and I want to look at the event loop more closely to see how this happens more precisely

[liveinjs]

@othiym23 @tjfontaine ,,

so,if

var delay = somefunction(){return somenumber };
var t2 = set Timeout(function(){ console.log("t2")}, delay);

the result is Uncertain ....

[tjfontaine]

Unref'ing a handle in general will result in less than predictable
scenarios if you're unaware of what else is holding the loop open. But
then again you're explicitly waking the event loop to not care about
that handle

[tjfontaine]

*asking not waking ... stupid autocorrect

[liveinjs]

thank you @tjfontaine

[trevnorris]

Think this is non-issue. Ping if this isn't the case.

[tjfontaine]

actually I still want to investigate this.

[jasnell]

@tjfontaine ... were there any followups on this?

[jasnell]

Closing due to lack of activity