javascript - Node.js setInterval() stops executing after 25 days - Stack Overflow

admin管理员组

文章数量:1277303

In my Node.js application, I use setInterval() to run a specific function every 1 hour. The function is executed properly for about 25 days, then the timer stops firing.

25 days seems awfully close to Node.js's TIMEOUT_MAX (2^31 milliseconds ≈ 25 days), but I don't really see why setInterval() should stop executing after that time.

Update:

I think this may have been caused by the following bug in Node.js: setInterval callback function unexpected halt #22149

In my Node.js application, I use setInterval() to run a specific function every 1 hour. The function is executed properly for about 25 days, then the timer stops firing.

25 days seems awfully close to Node.js's TIMEOUT_MAX (2^31 milliseconds ≈ 25 days), but I don't really see why setInterval() should stop executing after that time.

Update:

I think this may have been caused by the following bug in Node.js: setInterval callback function unexpected halt #22149

• javascript
• node.js
• setinterval

Share Improve this question Follow edited Aug 14, 2018 at 7:40 Moorglade asked Aug 14, 2018 at 6:51 MoorgladeMoorglade 31622 silver badges88 bronze badges 11

• Have you tried using a recursive setTimeout instead? – CertainPerformance Commented Aug 14, 2018 at 6:52
• 2 What is your code? – user202729 Commented Aug 14, 2018 at 6:54
• stackoverflow./questions/51826266/… – user202729 Commented Aug 14, 2018 at 6:56
• 1 Could you use something like cron / schtasks / some other OS-level scheduler instead? – Phil Commented Aug 14, 2018 at 6:57
• 1 @NoobTW I don't know about node-cron, but we were using node-schedule before and had the exact same problem. Anyway, it seems it's been fixed in Node.js now. – Moorglade Commented Aug 16, 2018 at 6:07

 |  Show 6 more ments

3 Answers 3

Sorted by: Reset to default 6

It seems the bug (#22149) has been fixed in Node.js 10.9.0.

It may be also worth noting that this bug seems to be influencing both setInterval() and setTimeout() (as reported here), so the workaround with setTimeout() in the callback function wouldn't work.

After reading the issue in github, I think they will fix it in the next release. If you need to work around before that, you can try recursive timeout instead. Checkout my code:

function doSomething() {
    console.log('test');
}

function doSomethingInterval() {
   doSomething();
   setTimeout(doSomethingInterval, 1000);
}

doSomethingInterval();

It's a known bug. Your easiest workaround is to use setTimeout instead, and then in your callback function call another setTimeout.

本文标签： javascriptNodejs setInterval() stops executing after 25 daysStack Overflow