Yeah, I just looked into that issue. It seems like some nasty memory corruption bug. I can reproduce it on my machine, but as soon as I change something (e.g. even just add some `println` for debug output), it disappears. It might be the fault of the `node-syscall` module or something might be wrong with Node.js 0.11.14. I don't really know what to do about it atm...