We've started seeing people experience this again today with the release node-sass@3.3.0.
This was resolved in fsevents@0.3.7 which I have confirmed locally.
However my research shows that it was reintroduced in fsevents@0.3.8 with the introduction of nan@2.
My investigation is in sass/node-sass#1107 (comment)
The segfaults stacktrace is
PID 47259 received SIGSEGV for address: 0x46
0 segfault-handler.node 0x00000001033c390f _ZL16segfault_handleriP9__siginfoPv + 287
1 libsystem_platform.dylib 0x00007fff8e80a5aa _sigtramp + 26
2 ??? 0x0000000103429870 0x0 + 4349663344
3 fse.node 0x00000001035d8616 _ZN3Nan3imp10GetWrapperIPFvRKNS_20FunctionCallbackInfoIN2v85ValueEEEENS0_15FunctionWrapperEEEPT0_T_ + 142
4 fse.node 0x00000001035d7a40 _ZN3fse8FSEvents10InitializeEN2v86HandleINS1_6ObjectEEE + 194
5 node 0x0000000100601047 _ZN4node6DLOpenERKN2v820FunctionCallbackInfoINS0_5ValueEEE + 725
6 node 0x00000001001749ee _ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE + 158
7 node 0x000000010019c97b _ZN2v88internalL19HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateERNS0_12_GLOBAL__N_116BuiltinArgumentsILNS0_21BuiltinExtraArgumentsE1EEE + 811
8 node 0x000000010019f1cd _ZN2v88internalL21Builtin_HandleApiCallEiPPNS0_6ObjectEPNS0_7IsolateE + 61
9 ??? 0x0000340e442060bb 0x0 + 57235877159099
My system
$ node -v
v2.5.0
$ npm -v
2.13.2
$ node -p process.versions
{ http_parser: '2.5.0',
node: '2.5.0',
v8: '4.2.77.21',
uv: '1.6.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
modules: '44',
openssl: '1.0.2d' }
$ node -p process.platform
darwin
$ node -p process.arch
x64
We've started seeing people experience this again today with the release node-sass@3.3.0.
This was resolved in
fsevents@0.3.7which I have confirmed locally.However my research shows that it was reintroduced in
fsevents@0.3.8with the introduction ofnan@2.My investigation is in sass/node-sass#1107 (comment)
The segfaults stacktrace is
My system