A Jazz musician turned developer and is excited about Node.js and its community. The fast turnaround from idea to working module has proven addictive for him and led to lots of modules which ended up on github and/or npm
Memory leaks are rare, but when they occur we need to be equipped to track them down. However not many resources exist that explain how to memory profile a Node.js application. In this talk I will explain how data is stored in the v8 heap and how to examine it using tools that are readily available on a developer's machine and are relatively easy to learn.
Additionally I'll show cutting edge features introduced to v8 that ease detection of memory leaks (i.e. memory allocation sampling). We will also discuss how to access these features via the v8 API even before they are exposed via Chrome's developer tools