Very hard failure with watch on OS X

[ronkorving]

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.

[shama]

This might have been fixed in chokidar see paulmillr/chokidar#167 and we just need to update the dep in watchpack.

[ronkorving]

The chokidar dependency in watchpack is already set to "chokidar": "^1.0.0", so it should be using the latest release.

[bebraw]

Should be fixed by now.

[ronkorving]

@bebraw Mind sharing why/how?

[bebraw]

@ronkorving Based on the above it was a chokidar issue. Is it still crashing for you then?

[ronkorving]

Based on the above, it wasn't. Watchpack at the time was already on the latest chokidar. It may be possible that it's fixed at the OS X level (seems possible given the comments on the issue mentioned above), or perhaps even chokidar. I have a hard time reproducing it now, but can't claim with certainty that based on anything tangible, the problem has actually disappeared.

On my end, nobody on the team working on that large project who had the issues still uses watch. I can ask for some people to try again.

[bebraw]

Ok, if you can repro, we can definitely re-open and mark this as a bug. That said, it's very hard to do anything about the issue if there's no concrete test case to run and debug.

[ronkorving]

Understood

[grimen]

I ran into this issue too after updating some NPM libraries for hobby project to latest tags. I guess I will downgrade libs until it works again.

[ds3783]

I met the problem, it seems a mac OS's bug, after I reboot my mac, it disappear.

[Andyczc]

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

[ronkorving]

@Andyczc Which version of Webpack?