Hunting memory leaks issues is a complex problem with fiendish edge cases, and debugging them can be a daunting task. To avoid such a problem in your app, you need awareness about it and constant vigilance.

JavaScript memory leaks are sneaky and could be challenging to localize because they can go unnoticed for some time. And even if your performance gets progressively worse, you will not see a thrown error on the browser while running the leaking app because it’s not an invalid code that causes memory leaks, but a logical flaw in it.

In this course, we’ll see how to effectively track memory leaks down and learn what causes them. You’ll get insights on how to respect more the end-user device’s resources. You’ll also avoid situations where you pull your hair out trying to understand what’s going on with your performance.

I designed this course to suit newcomers as well as advanced developers, and I will walk you through the topic step by step until you get your hands dirty.

At the end of the course, you’ll be able to identify, diagnose, and fix memory leaks in web apps even if you’re not the one who implemented them. You’ll be also able to catch patterns in your source code that cause leaks.