Very hard failure with watch on OS X

We are running a fairly large project with 922 JavaScript and .less files being watched by Webpack’s watch function on OS X (10.10.2) running on Node.js 5.2.0. During the initial build, or right when it’s done with that, the following happens:

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop: failed to create the cffd
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamCreate: _FSEventStreamCreate: ERROR: could not open kqueue
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStart(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamUnscheduleFromRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamInvalidate(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamRelease(): failed assertion 'streamRef != NULL'

I’ve made an issue about this at libuv/libuv#645, but I was wondering if this is something other Webpack users have also suffered from and if a workaround is known. Thanks.

Author: Fantashit

7 thoughts on “Very hard failure with watch on OS X

  1. I also met this problem on the iterm, my solution is to put the iterm closed to restart again, to solve

  2. Just to add to the mix. My mac soft crashed on me (back to the login screen), logged back in, and was getting this. Restarted iTerm and all was good. Thanks everyone.

  3. Just my 2 cents, but IMHO having to restart your terminal is not a fix. Somewhere, something is broken. I’m not saying that’s Webpack, but something is broken. So I wouldn’t want to dismiss this as a non-issue, simply because it’s “fixed” for everyone.

  4. Restarting iTerm fixed it for me too, thanks. @ronkorving you are absolutely right, but it is iTerm in this/my case, because things like starting ssh sessions also stop working at the same time.

Comments are closed.