Bus Error on Mac OS 10.9 DP8

[BernhardValenti]

getting a bus error crash when running coffee with -w, I suppose this is an issue with node. node 0.10.18 with mac os 10.9 dp8. this is the output when run from a debugger:

* thread #2: tid = 0x143349, 0x00007fff964bd583 CarbonCore`FSEventsClientProcessMessageCallback + 39, stop reason = EXC_BAD_ACCESS (code=2, address=0x1007f5f48)
    frame #0: 0x00007fff964bd583 CarbonCore`FSEventsClientProcessMessageCallback + 39
CarbonCore`FSEventsClientProcessMessageCallback + 39:
-> 0x7fff964bd583:  callq  0x7fff964add4d            ; FSEventsD2F_server
   0x7fff964bd588:  movq   (%rbx), %rax
   0x7fff964bd58b:  cmpq   -16(%rbp), %rax
   0x7fff964bd58f:  jne    0x7fff964bd59b            ; FSEventsClientProcessMessageCallback + 63

[bnoordhuis]

/cc @indutny - not sure if we want to accept bug reports for Developer Preview versions of OS X but I'll let you decide.

[tjfontaine]

we probably should try and get ahead of this, I have a dev account and a laptop at home I can use for such things, I'll get it upgraded this weekend in preparation

[neekey]

Same problem, reference to this issue: gruntjs/grunt-contrib-watch#204

[indutny]

@tjfontaine any news? Can you post FSEvents.h as a gist and send me a link?

[bnoordhuis]

I've rolled back the v0.10 FSEvents changes in joyent/libuv@38df93c. We'll revisit this in master.

[eendeego]

I'm also seeing this on 10.9 Developer GM seed.

[glasser]

@bnoordhuis Do you think this is worth putting out a 0.10.21?

[eendeego]

(My 2cents) The next apple event will be held on Oct. 22nd and the GM is already (limitedly) out, therefore, both 0.10.21 and 0.11.8 would be nice.

[tjfontaine]

My plan would be for a v0.10.21 next Tuesday.

[indutny]

@tjfontaine I've checked headers, and there're no breaking changes or deprecations to this API in OSX 10.9.

[eendeego]

@indutny I've started to investigate this issue (see #6269), and it seems that the it breaks when CFRunLoop tries to call the application (in this case, node's) callback.

The code on libuv related to this isn't exactly trivial, can you provide some hints on how to go further ?

BTW: After going back to 0.10.17 (as suggested on that issue), I've noticed that things that rely on FSEvents (in my case, grunt-watch/regarde) work much more reliably.

[dviramontes]

confirmed, downgrading to v0.10.20 fixes
Waiting...Bus error: 10

Thanks.

[indutny]

Should be fixed by joyent/libuv#964 (comment). Leaving it open until merging into node.

[johannesnagl]

upgrading to the latest version (0.10.21) worked for me on #mavericks.

[indutny]

Fix landed in libuv's master should get into node.js master soon: joyent/libuv@0fdd99f

[kevinsimper]

I get this error on 0.10.32 when using gulp.watch

What did error come from? Too many files to watch or how?

Here is my gulp file:

var gulp = require('gulp');
var sass = require('gulp-sass')

gulp.task('sass', function () {
    gulp.src('www/**/*.scss')
        .pipe(sass())
        .pipe(gulp.dest('./www/build/'));
});

gulp.task('compile', ['sass']);

gulp.task('default', ['sass'], function() {
    gulp.watch(['www/**/*.scss'], ['sass']);
});

[indutny]

The error came from the stack limit that we was using: https://github.com/joyent/libuv/pull/964/files , but it should be technically fixed.

[kevinsimper]

It is confusing, because it came without I did any upgrade or npm installments. I do not have any idea where to look.

$ gulp
[11:57:36] Using gulpfile ~/node/project/gulpfile.js
[11:57:36] Starting 'sass'...
[11:57:36] Finished 'sass' after 5.18 ms
[11:57:36] Starting 'default'...
[11:57:36] Finished 'default' after 135 ms
Bus error: 10

[indutny]

Could you please do a following thing:

ulimit -c unlimited
gulp
lldb -c /cores/core...
bt

and paste results here?

[kevinsimper]

I tried your commands but could not figure out lldb -c /cores/core... and bt does not exist on os x.

But i found the bug, i switched node-sass out with ruby sass, and that showed that there was an import loop. Going to open a issue on node-sass.

Thanks for your help 👍 I did search a lot and the only useful thing that showed up was this.