You can check out this video to learn more about hurl http://vimeo.com/6238577
You can check out this video to learn more about hurl http://vimeo.com/6238577
Using a fork per request is the easy way out. The problem as you've all seen, is that memory will be used up very very quickly.
The solution is to rewrite the app to use an event loop like select or epoll, or to queue the requests in a message queue: doable, but worth the effort? I doubt it, since the website looks like a hobby rather than a commercial product.
That is, if someone forks hurl (http://github.com/defunkt/hurl) and rewrites it to use one of the fixes you referred to above, I'm sure they'd merge that in and deploy that.
Doing it with Resque would make a lot of sense since hurl uses Redis already.
I'm saying that's probably why Chris and Leah haven't fixed it already and probably for many days to come.