Repository navigation
setTimeout eating CPU time and doing infinity stuck with non-whole delay #24897
Description
- Version: 11.3.0
- Platform: Windows (possible affected another platforms too)
- Subsystem: Timers
setTimeout eating CPU and cant fire if delay is non-whole number.
Can be easily reproduced even from node-cli:
setTimeout(()=>{console.log("timeout fired!")}, 880.0000000000001)Working example:
setTimeout(()=>{console.log("timeout fired!")}, Math.round(880.0000000000001))Possible related issue from past: nodejs/node-v0.x-archive#8065
Update: it working sometimes
Activity
richardlau commentedon Dec 7, 2018
Possibly addressed by #24819?
cc @nodejs/timers
targos commentedon Dec 7, 2018
It was fixed in #24214 and just released in Node.js 11.4.0