-
-
Notifications
You must be signed in to change notification settings - Fork 37.3k
Timeouts sometimes not fired on Linux/ARM #2326
Copy link
Copy link
Closed
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().Issues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
Description
Activity
Metadata
Metadata
Assignees
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().Issues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
I'm having a problem where long (1 hour) timeouts registered via setTimeout() are not fired if the process has been idle for a while. If I then trigger some I/O by loading a page, the past-due timeout is immediately fired. Inspecting with gdb while in this 'hung' state shows that it's sitting in epoll_pwait():
I don't know if epoll_pwait() is exceeding/ignoring the timeout or what. Will do some more digging. This is running on a BeagleBone Black under Ubuntu Trusty, kernel 3.14.