-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Node finished with non-zero exit value 139 #5769
Comments
Exit code 139 typically means a segfault (128 + 11 (for segfault)). Is it possible you can try running it under gdb or similar and getting a backtrace? I'm curious if this is the same issue as #5768. |
Thanks for the full repro repository that really helps :) |
While trying to capture the segfault, I learned something new about looking at Apple crash reports!
|
Yep - this looks like a dup of #5768. |
For future reference if anyone is trying to get a backtrace on Mac OS X when node has a segfault, take a look at http://stackoverflow.com/questions/9412156/how-to-generate-core-dumps-in-mac-os-x for where to find Apple's crash reports. |
Appears to be fixed in Node 5.9.1. |
Was as well experiencing this in Node 4.3.0 on OSX, appears to be fixed in Node 4.4.5. Thanks guys for your hard work! |
This issue only started happening after I upgraded Node from 5.8.0 to 5.9.0. I have a local repro that happens pretty much 100% of the time. I have tried to create an example that causes this to happen. It doesn't occur 100% of the time, but when run in a loop it will eventually occur. See https://github.com/nmalaguti/repro-grunt-node-5.9.0 for details about how to run it.
Gradle is running Node to run Grunt. I don't know what error 139 means.
The text was updated successfully, but these errors were encountered: