Finding a Ruby memory leak using time analysis | Dark Hacker News