-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Segmentation fault in node v4.8.3 #13966
Comments
/cc @nodejs/v8 |
Looks like memory corruption. What happens when you don't load bcrypt and ursa? |
@bnoordhuis same issue. |
Can you post the stack trace + pmap dump? (What OS X calls 'images'.) |
I've generated the dump but it shows some confidential data. Could you guide me on how to debug this further? Or say what would you like to see? |
@bnoordhuis would building a node.js binary with debugging symbols enabled help in this case? |
@Rush It would. If nothing else, it has many more sanity checks so it will probably catch the bug closer to the source. @kessiler Maybe the first 10 or so stack frames? I'd also would like to know what libraries and .node files, if any, are loaded at the time of the crash. Or is that the confidential data you were referring to? That would make it hard to help. |
@bnoordhuis I don't know if this is even related because it happens on each run.
compiled node 4.8.3 with |
@Rush Are you using faye? That error and stack trace is eerily similar to #13351, which was the result of faye monkey-patching internals. See also faye/websocket-driver-node#21. |
@bnoordhuis a node module "nforce" that we rely on is using "faye". |
Okay, that would explain it. Get rid of the module (or fix the upstream bug) and the crash should go away. Let me know if you still have issues afterwards and I'll reopen. |
Version: v4.8.3 (official build)
Platform: Linux railsonfire_73606f4b-2d1a-446e-bc26-6743fadb8e0e_e79b84805f8c 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (Codeship)
Subsystem: v8
It's happening randomly when running integration tests and I have no idea why.
Here's the stack trace:
I was also able to reproduce in my OSX laptop, however, it doesn't happen so often.
Here's the stack trace:
The text was updated successfully, but these errors were encountered: