fsevent_watch bomb on OSX.

[sblackstone]

I've got a program I'm developing that uses background process that loads rails (delayed_job & clockwork). Having these two processes up plus a rails console causes 3 sets of fsevent_watchers to be started until I eventually hit the OS-level process limit and start getting "cannot fork" errors.

Perhaps perhaps the listen functionality could be moved into spring so that we only watch each file once?

[WaKeMaTTa]

:penguin:

[molefrog]

@sblackstone I'm experiencing the similar problem after an upgrade to Rails 5 (the spring has been upgraded as well probably). Any idea what is causing it?

UPDATE: It might be something that is not directly related to spring in my case, but you may want to check this epic thread if you haven't yet: https://github.com/rails/rails/issues/26158

[sblackstone]

@molefrog Rails itself has event watchers and each instance of Rails you start is going to start N worker processes to monitor files for changes.

I created this issue as a suggestion that spring could handle this so that there would be a max of one file process per file..

[kfiltschew]

try to upgrade listen gem like it is referenced here: https://github.com/rails/rails/pull/37896