You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
in 0.6 the second console.log also never fires (intended behavior).
Actually, it's the other way around. Both timeouts should fire immediately (that is, after the shortest possible interval) because that's what browsers do for timeouts > 2^31-1 and we follow browser behavior.
The fact that a timeout of 835371139071 doesn't actually work like that is due to an unfortunate bug: ~~835371139071 == 2147483647 which is exactly 2^31-1. See #3607 for details.
This
console.log
does not fire (at least for some years):while this one fires immediately:
This behavior has changed since node 0.7.x, in 0.6 the second
console.log
also never fires (intended behavior).What value is 835371139072 ? (This is the same for x64 and ia32).
The text was updated successfully, but these errors were encountered: