Debugging a Production Memory Leak in a React + Node.js Application (opens in new tab)
# My Node.js Server Was Leaking Memory in Production. Here's How I Found It. * * * Our Node.js server was crashing in production. Not once — every single instance was going down, one after another, and Sentry (logging) was flooding with alerts. We had auto-scaling configured with a minimum of 3 instances and a maximum of 10. So users weren't getting hit directly — as one instance crashed, another spun up to replace it. But every new instance had the same code, the same leak. It was a contin...
Read the original article