Tracking down a memory leak in Ruby's EventMachine
This is slightly off-topic, but I worked on a Ruby project where we did something just like this:<p>"It was easy enough to work around the leak by adding monitoring and restarting the process whenever memory usage grew too large"<p>I was surprised, because I can not think of any other language and/or framework where "just restart the process" is done so often. I mean, this is not a common attitude among Java programmers, I don't think it is common among C programmers, and I don't think it is common among Python programmers. But it does seem to be fairly standard in the Ruby community. David Heinemeier Hansson admitted this used to happen with Basecamp:<p><a href="http://david.heinemeierhansson.com/posts/31-myth-2-rails-is-expected-to-crash-400-timesday" rel="nofollow">http://david.heinemeierhansson.com/posts/31-myth-2-rails-is-...</a><p>Can anyone else tell me of a community where this is done so commonly?