How to find production memory leaks in Node.js applications?

The post details the process of identifying and fixing a memory leak issue in a Node.js API deployed on Kubernetes. It discusses the investigation approach, including attempts to reproduce the issue locally, load testing in staging environments, and taking memory snapshots from production. The post highlights the use of tools like Clinic.js, Jenkins, and Chrome DevTools, and emphasizes the importance of proper debugging and risk mitigation strategies in production. Ultimately, the issue was traced to the improper handling of grpc connections in the Google reCAPTCHA enterprise library.