-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeouts sometimes not fired on Linux/ARM #2326
Comments
I should add this was with io.js 2.4.0 and 2.5.0. I haven't been able to test 3.0.0 due to some incompatibilities with modules, but I'll try to write a small test case to use there. |
Maybe this is related to #2232 |
It's probably related to libuv/libuv@d1b5008 - the timeout value is exactly What happens when you lower |
cc @snorp could you try what @bnoordhuis suggested? (You'll need to build io.js yourself to do it.) |
Oops, I forgot to comment here. I did build io.js myself with the suggested change, but it crashed on startup for some reason, and I haven't had time to look into it more. I did add a recurring 15 minute timeout to my app and it seemed to keep things from getting into this busted state. |
No follow-up, closing. |
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.
The text was updated successfully, but these errors were encountered: