node. js Memory Leak Location

Before we used node. JS on a 64-bit Linux server, when the node process physical memory approached 1.6G, the memory limitations of the Google V8 engine caused the process to exit!

Obviously we have a memory leak problem with our own code or the 3rd line module of NPM loading, so how do we go about locating it?

Common Debugging Tools:

1. V8-profiler
2. Node-heapdump
3. Node-mtrace
4. DTrace
5. Node-memwatch

Specific positioning methods can be consulted:

https://hacks.mozilla.org/2012/11/tracking-down-memory-leaks-in-node-js-a-node-js-holiday-season/

Http://www.oschina.net/translate/tracking-down-memory-leaks-in-node-js-a-node-js-holiday-season

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

node. js Memory Leak Location