SO WE'VE GOT A MEMORY LEAK…

Summary from the TLDR Web Dev newsletter

This developer tackled a memory leak in his high-traffic Rails app by analyzing heap dumps and using tools like rbtrace, heapy, and sheap. The root cause was traced to a combination of an issue in ActiveSupport::Subscriber and invalid URIs processed by the Bugsnag gem. He goes over his debugging process throughout the article.