Fixing production memory leak
Investigating and fixing memory leak in Node.js API server
Created: 11/28/2025, 1:14:25 AM
Updated: 12/1/2025, 1:14:25 AM
Channel: general
Context Items
3 itemsDecisionHigh11/30/2025, 1:14:25 AM
Sign up to edit
Sign up to delete
root_cause
Memory leak traced to unclosed database connections in the connection pool. The pool was not properly releasing connections after timeout, causing gradual memory growth.
ProgressNormal11/30/2025, 11:14:25 PM
Sign up to edit
Sign up to delete
fix_applied
Added connection.release() in finally blocks. Set pool max connections to 20 with 30s idle timeout. Added connection health checks every 60s.
NoteNormal12/1/2025, 1:14:25 AM
Sign up to edit
Sign up to delete
monitoring
Added Prometheus metrics for connection pool size, active connections, and memory usage. Set up alerts in Grafana for when memory exceeds 80% threshold.