40 MB an hour: the Node memory leak hiding behind setMaxListeners(0)
A postmortem of a slow leak in a Node ingest service: how two heap snapshots, one retainer chain and a silenced warning led us to the bug.
Node.js platform engineer
Tobi Okeke
Tobi runs the Node services behind an events API and has read more heap snapshots than he would like. He writes about memory, the event loop and the runtime flags that save a release.