Hacker News Reader

> I run a massive Node application and never had any issues with memory leaks. I wouldn't even know how to forcefully create one even if I wanted to.

(1) I have no leaks and (2) I don't know how to create them -- These don't really square with each other.

Leaks are easy. TFA mentions the classic one in UI apps: when you don't remove event listeners.

View on HN

> (1) I have no leaks and (2) I don't know how to create them -- These don't really square with each other.

If he runs his service for a long time and the memory usage doesn't keep growing, no resource exhaustion problem occurs, then he can reasonably say he has no leaks. At least, he has no significant leaks.

I don't have to know how to create nuclear bomb to know I don't have one.

Yes, but this is not an UI app. I don't think I have leaks because memory sits at a fixed percentage even though I get hundreds of requests a second.

Reply on news.ycombinator.com