Most Memory Leaks are Good - Shopify

This post details a specific incident of a production memory leak caused by a C extension in a memcached client library. It highlights the difficulty in reproducing the leak, the limitations of general Ruby memory profiling tools (memprof, memprof.com) when the leak is in C code, and the eventual success in identifying and fixing the issue through reproducible local testing, teamwork, and a hunch about memcached client behavior. The post also provides advice on making leaks reproducible, trusting hunches, and collaborating with others.