Get the latest tech news

So We've Got a Memory Leak

A story of finding, understanding, and fixing a memory leak in our Rails app. With graphs and code!

We went looking at the stable branch for the version of Rails we’re currently on (6.1) and found that it’s basically a per- ThreadHash used to store lists of ActiveSupport::Subscriber instances, based on the event name. Our fix, in the short term, was to upgrade the Bugsnag Gem to a version that included the “don’t raise an error while trying to clean an invalid URI” change. And dismissed it as not being related because… why the heck would redacting part of a URI, something the Bugsnag Gem already did in other places, cause such a bad and sudden memory leak!?!?

Get the Android app