-
Notifications
You must be signed in to change notification settings - Fork 42
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
Two dictionaries - Segmentation fault: 11 #18
Comments
I'm unable to reproduce this, but I would encourage you to productionalize your code to get it running. Try using |
I've two minimal examples here: https://dl.dropboxusercontent.com/u/8989748/nodehun-segfault.zip . One uses And you are right, |
short answer: I don't really know long answer: node.js, itself, has a few issues on OSX (as does Python, Ruby, PHP, etc), because OSX has weird configurations that violate what BSD and Linux normally do. This is usually a security thing (i.e. no process on OSX is allowed to have more than 2048 file descriptors at a time). Seg-faults are common. On the whole OSX is a fine OS to do work on, but it isn't a perfect representation of *nix in production. Developers working on projects like Node.js, Python, etc are usually content to let more obscure bugs in OSX slide, because it is assumed you won't actually be running production code on OSX. |
nodehun version - 1.0.2
node version - v0.10.36
OS X
The text was updated successfully, but these errors were encountered: