-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Unhandled thrown error in cluster module: #3341
Comments
You might be better served asking in the Help repo: https://github.com/nodejs/help/issues If you do, be sure to include the relevant parts of your source code. |
@Trott I'm not really asking anything - I just wanted to report the bug. I'm assuming it's a bug, since the cluster module shouldn't be throwing errors right? Please correct me if otherwise though. Please could you remove the question tag? (I've edited the post now so it doesn't look like a question). |
Ah, I misunderstood. Sorry about that, and thanks for the clarification. |
I'm going to close this, it's a duplicate of #3072. @bgSosh If you have a way to reproduce it, can you post it in that issue? Thanks. |
@bnoordhuis Ah sorry, didn't see that issue. I have no way to reproduce it unfortunately :( |
@bgSosh, feel free to add what you know to #3072. |
@Zarel Will do (though I don't have much). |
I got this error shortly after cluster child processes died:
Node 4.1.1
The text was updated successfully, but these errors were encountered: