-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
runInContext breaks node process #13464
Comments
Any updates on this one, is it already backported to the LTS? |
There's a good chance it'll go into 6.11.1. |
The problem reproduces with 6.11.1 and 7.10.1 The code above works fine with 8.2.1 |
The fix was applied to 6.11.2 two weeks ago, see #14373. I just checked and it seemed to work fine (endless loop). I'm closing this. Let me know if I misunderstood and this should remain open. Thanks for reporting! |
Works like charm. Thanks for the fix |
When the following code is executed:
Node 6 & node 7 on both Mac & Linux, it bails out with exit code
0
, instead of looping endlessly. We get 2 to max 80 iterations without any exception logged.Interesting is also the fact that under high load in containerized environment (Cloud Foundry's Garden) the context execution blocks. Even with 1000 ms timeout it never returns or throws exception. We observed a call hanging for > 48 hours.
With node 8 the code works correctly and we get the expected endless loop with occasional exceptions due to the extremely low timeout.
The text was updated successfully, but these errors were encountered: