Why Puppeteer's 'Simple' Memory Leaks Are Killing Your Node.js Containers
Your Puppeteer bot runs fine for 10 minutes, then balloons to 2GB and gets OOM-killed. Sound familiar? Time to profile like a pro, not guess.
⚡ Key Takeaways
- Puppeteer's leaks hide in Chrome child processes, not Node heap – monitor RSS and external first.
- Use JSONL time-series tracking and heap diffs to pinpoint retainers like rogue pages.
- Recycle browsers, ruthless page closes, and lean args prevent 90% of OOM kills.
Worth sharing?
Get the best Developer Tools stories of the week in your inbox — no noise, no spam.
Originally reported by dev.to