Two dictionaries - Segmentation fault: 11 about nodehun HOT 3 CLOSED

I'm unable to reproduce this, but I would encourage you to productionalize your code to get it running. Try using readfile instead of readFileSynce and try running this on linux to see if it works. I've chased too many OSX segfaults to care about it (the OS) as anything more than a dev environment.

from nodehun.

I've two minimal examples here: https://dl.dropboxusercontent.com/u/8989748/nodehun-segfault.zip . One uses readFile, the other one uses readFileSync.

And you are right, readFile does work. But why does it behave differently than readFileSync?

from nodehun.

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.

from nodehun.