Detecting Node.js Memory Leaks with devtool

Even during a holiday the author felt the need to tinker and decided to share a step‑by‑step guide on detecting memory leaks in Node.js.

Memory leaks can occur in any language, including Node, when memory is consumed faster than it is reclaimed; therefore it is crucial to detect them early.

The article recommends devtool as a convenient tool for this purpose, alongside more well‑known utilities such as memwatch and heapdump .

Installation is straightforward:

npm install devtool -g

If the installation fails due to the Electron dependency being blocked, the fix is to delete the existing Electron folder in node_modules and reinstall it from a mirror:

ELECTRON_MIRROR="https://npm.taobao.org/mirrors/electron/" npm install electron -g

Next, create a script memoryleak.js that intentionally leaks memory by pushing data into an array on each HTTP request.

Run devtool to watch the script:

devtool memoryleak.js --watch

The tool opens a UI where you can take a heap snapshot via the “Take Heap Snapshot” button; the first snapshot shows a baseline memory usage.

After issuing several HTTP requests (e.g., refreshing 127.0.0.1:3000 ), take another snapshot. The UI will display increased memory usage (e.g., 6.3 MB → 8.8 MB → 11.9 MB → 13.4 MB), indicating a leak.

By comparing the two snapshots and examining the “All objects” view, you can identify objects whose size grew and pinpoint the leak source, highlighted in the screenshots.

The “Timeline” tab visualizes memory consumption over time; a stair‑step pattern in the graph further confirms the leak.

Finally, the article notes that devtool offers many additional features for Node development beyond leak detection, encouraging readers to explore them and wishing everyone a happy holiday.