Summary: if you encounter "Bus errors" or "Segmentation fault" when adding or refreshing a channel: a) Upgrade to 0.6.9 or later and b) turn off REMEDIE_DEBUG environment variables if set.
We've confirmed that since 0.6 release there are very rare cases that your Remedie Server process crashes with "Bus errors" or "Segmentation fault". There are a couple of ways to reproduce this.
If you set the debug environment variable REMEDIE_DEBUG, Log::Dispatch apparently gets confused with Coro's context switch in the loop and gives a bus error. Turning off the environment variable would be the solution to avoid this.
Alternatively, when you start the server process while Remedie UI is open in your browser, and you add a new channel without first reloading the page would cause the bus error, at least on Mac OS X.
This has actually been a deal breaker for the OS X first time users since it should always happen and they couldn't add any channels. I tracked down to find some issues with JSON::XS encoded data and perl reference counter with Coro multitasking, so I added a workaround which hopefully fixes the problem. This patch is now included in the 0.6.9 update.
We'll continue to chase this bus errors or segmentation fault bug with Issue #145. If you encounter the problem, reporting it with a reproducible step and/or gdb backtrace would be valuable.
