This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
unrefed interval timers not firing as expected in 0.10.34 #8900
Comments
Just at a guess, in 0d05123, at timers.js:296:
Should that be |
Thank you @ploer for reporting the issue and looking into it. Indeed, the issue seems to be caused by 0d05123. @trevnorris could you please take a look? |
ploer
added a commit
to node-saml/passport-saml
that referenced
this issue
Dec 18, 2014
misterdjules
pushed a commit
to misterdjules/node
that referenced
this issue
Dec 19, 2014
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes nodejs#8900.
@misterdjules , thanks for the quick response & for all your contributions to node! |
@ploer No problem, it's a team effort! Hopefully we'll be able to communicate soon when these fixes will be released. |
misterdjules
pushed a commit
to misterdjules/node
that referenced
this issue
Dec 19, 2014
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes nodejs#8900. Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
mscdex
pushed a commit
to mscdex/node
that referenced
this issue
Dec 25, 2014
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes nodejs#8900. Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
jasnell
pushed a commit
to jasnell/node-joyent
that referenced
this issue
Jan 5, 2015
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes nodejs#8900. Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
Fishrock123
pushed a commit
to Fishrock123/node
that referenced
this issue
Apr 2, 2015
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes: nodejs/node-v0.x-archive#8900 Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
indutny
pushed a commit
to indutny/io.js
that referenced
this issue
Apr 3, 2015
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes: nodejs/node-v0.x-archive#8900 Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
indutny
pushed a commit
to nodejs/node
that referenced
this issue
Apr 3, 2015
This change fixes a regression introduced by commit 0d05123, which contained a typo that would cause every unrefd interval to fire only once. Fixes: nodejs/node-v0.x-archive#8900 Reviewed-By: Timothy J Fontaine <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-by: Trevor Norris <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It appears to me that after upgrading to 0.10.34, a setInterval() call that is unref()ed will only fire once and then not recur.
Example code:
Output on 0.10.33, which is as expected, and 0.10.34, which only fires once and then doesn't recur:
Not sure if this is related to issue #8897, but the symptoms seem quite different, and although I've encountered both of them they were in different circumstances.
The text was updated successfully, but these errors were encountered: