This guide explains how to automatically capture Java OOM heapdump files using a DaemonSet that watches for heapdump.prof creation, compresses and uploads them to Alibaba Cloud OSS, and notifies developers via a WeChat bot, providing a scalable, non‑intrusive solution for memory‑leak diagnostics in Kubernetes environments.
A production outage at Company A was traced to an incorrect JVM -Xmn setting that matched -Xmx, causing the young generation to consume the entire heap and repeatedly trigger Full GC and OutOfMemoryError, a lesson on careful JVM tuning and script management.
After releasing a new version of a VSCode extension, intermittent freezes were traced to a memory leak; the investigation used llnode and heapdump, tackled Electron version mismatches, extended DevTools parsing limits, and ultimately identified recursive socket callbacks as the root cause.
This article recounts a real‑world incident where a simple JSON.parse() try‑catch block triggered a massive memory leak in a Node.js 12 application, explains how the V8 engine’s script_list retained orphaned script objects, and shows how tools like gdb, llnode and heapdump can be used to locate and fix the issue.
