Demystifying Memory Leaks in JavaScript

Want to master Fullstack: JS Backend, DevOps, Architecture? Join a two-day conference on all things Node.js, gathering Back-end and Full-stack engineers across the globe in the cloud is here to help you staying up-to-date on the latest Node.js tech.

Node Congress

I’m attending @NodeCongress, the biggest conf on #JavaScript backends – by clicking the badge you may get a free remote ticket & join me there with 5k other #nodejs devs & 15 great speakers #deno #cloudflare #awscloud

Node Congress 2021

Ruben Bridgewater

Today it is possible to write complex applications with only a handful of developers in a short time frame relying upon Frameworks and tooling. But what happens when the application crashes with out of memory errors? How is it possible to guarantee fast response times? These problems are still considered difficult to solve.Let's dive into the Node.js internals and learn about profilers and the garbage collector. Understanding how the system works in depth let's you write code that is safer, faster and less error prone.Let's make sure you always provide the best experience for everyone. Yourself and your customer. Let us find that memory leak and fix it.Learnings<ul><li>        Participants understand the Node.js memory handling and their shortcomings.</li><li>        Participants know when to profile their application to identify memory leaks and slow code.</li><li>        Participants are able to find and address most memory leaks.</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>