Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FSEventStream woes #281

Closed
aMoniker opened this issue Jan 16, 2014 · 2 comments
Closed

FSEventStream woes #281

aMoniker opened this issue Jan 16, 2014 · 2 comments

Comments

@aMoniker
Copy link

I'm running grunt-contrib-watch v~0.5.3 with node v0.10.24 and npm v1.3.21 on OSX Mavericks.

When I run grunt with my default task set to watch, it's fine until I change a file, at which point I get:

(CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)

I'm using ['**/*', '!**/node_modules/**'] to watch, which I assume has something to do with the problem. OSX doesn't allow that many files to be watched at once or somesuch.

@shama
Copy link
Member

shama commented Jan 16, 2014

That is a bug in node (that should have been fixed but maybe not released) with watching a large amount of files. See nodejs/node-v0.x-archive#5463

Do a grunt watch --verbose and make sure it's not watching more files then you need.

@aMoniker
Copy link
Author

Yeah, looks like some people are having luck downgrading node to 0.10.17, but that doesn't seem to work for me.

Thanks for suggesting using verbose mode, there were definitely some vendor directories I didn't need to watch :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants