You Don't Know Javascript Yet! Performance Optimization | Chakde System Design Ep. 11

This episode is part of Memory leak in Javascript & Performance optimization techniques for web apps, which is covered in multiple episodes of Chakde System Design.

0:00 Introduction
1:26 Accidental global variables
6:50 Forgotten timers or callbacks
9:26 Remove listeners if not required
14:53 Out of DOM references
18:58 Closures
23:15 Reference object cycle
27:12 Detached window
31:07 Promises, Observables, EventEmitters forget to stop listening
33:03 IntersectionObserver, ResizeObserver, MutationObserver forget to disconnect
34:39 Virtualization of DOM
37:19 Thank You Note

In case you have missed other episodes of the #ChakdeSystemDesign series, do check out :

Connect to learn & grow together in our career❤️:

#Javascript #performance #optimization #PerformanceOptimization #WebApps #NetworkOptimization #SystemDesign #FrontendSystemDesign #frontend #interview #frontendInterview #interviewQuestions

[praveenchukka]

You seem so excited doing these things. It’s contagious 😊. Loved the video 👍🏻

[ganeshshetty]

Every time i watch your video i would feel i know only 1% about front end development, By the way great work Chirag

[arunkaiser]

THE BEST VIDEO on Memory leak, Thank you

[prasenjitsutradhar]

Sir please upload more videos on system design....Or you could make video real Machine coding interview problems, how to handle such interviews. You can post a small video as a challenge for viewers & then few days later, you come up with the solution. This will definitely help us!😊❤

[sudiptasaha]

Hello Chirag, there is some issue with the audio. it seems the audio is very low even though i have increased the volume to max level. please do check on this.

[artofcoding]

Nice examples to illustrate memory leak...quite informative

[lolnoob]

for out of dom references, what if refernce is saved in const, is there a need to clean? Or if using const you should not call it in global scope?

[-cs]

But what is it's use in real life? These things are not useful for JS Frameworks as most of it are present by default or its very generic use cases

[shubhampawar]

This is average at best. I don't consider myself a JavaScript expert, but I've learned these things 3 months into my JavaScript journey. Also, experts are using typescript and not JavaScript, which will flag all these errors. Even if you're not using typescript, ESLint will catch these silly mistakes