Debugging a Memory Leak in a Third-Party Library: Our Forking Journey

How we identified the culprit, submitted a patch, and maintained our own version temporarily.