Existing Ruby tooling is quite helpful when investigating memory leaks if and when we can reproduce them on our development machine or staging environment. But what about those cases when the memory leak only really shows up in Production? Perhaps over a long time period?
Together, they can be used to provide low-overhead heap sampling, enabling the investigation of Ruby memory leaks in production.
You can find the video and slides for the talk below! And as always, feedback is very welcome!