Skip to content

Comment on Debugging Node.js memory leaks

Comments

Some great lessons in this post:

* open()/close() (in other words: resource management) are as likely to cause leaks as malloc()/free() (aka memory management)

* Single threaded code can have race conditions

* No single tool (debugger, heap profiler, logging, etc) will be a panacea for troubleshooting production

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.