Workaround: using Guard groups and running LiveReload from a separate guard instance (e.g. bundle exec guard -g livereload, given LiveReload has it's own group).
Probable cause: calling fork() messes up the threads in EventMachine in LiveReload
Possible solution/workaround: fixing LiveReload to run itself in a fork, so it's isolated from other fork() calls
Depends on server config used.
Workaround: using Guard groups and running LiveReload from a separate guard instance (e.g.
bundle exec guard -g livereload, given LiveReload has it's own group).Probable cause: calling fork() messes up the threads in EventMachine in LiveReload
Possible solution/workaround: fixing LiveReload to run itself in a fork, so it's isolated from other fork() calls