-
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
GC segfault #11606
Comments
Can you try excluding bcrypt and segfault-handler? You can still get stack traces if you turn on core dumps ( |
@bnoordhuis I removed |
You could try running node in gdb: If that isn't an option either, I suppose you should talk to your system administrator. |
No follow-up, I'll close this out. |
Node crashed during the Garbace collection but without any other high level pattern (maybe related to #3715).
Unfurtunately I don't have any code to reproduce as I was not able to isolate the problem.
This is the crash stack trace captured with segfault-handler module:
And also this other stack sometimes:
Additional information:
Node framework: express, Sails.js
My native modules founded with
find node_modules -name '*.node'
are:The text was updated successfully, but these errors were encountered: