JavaScript Memory Leaks and How To Fix Them

preview_player
Показать описание
Memory Management in JavaScript is often not a topic, but to avoid Memory Leaks in your web apps it's crucial to have a good understanding of how the Garbage Collector works, what can cause a Memory Leak, and how to analyze Memory Leaks with Chrome DevTools. In this video, I'm going to explain all of that.

======⚡⚡⚡======
======⚡⚡⚡======

📚 Resources:

🕒 Timestamps:
(00:00) Memory Leaks explained
(03:57) Causes of a Memory Leak
(08:05) Identifying Memory Leaks

And don't forget to subscribe for more videos like this 😊
Рекомендации по теме
Комментарии
Автор

And how do YOU guys detect and overcome memory leaks in your projects? Feel free to share your approaches below 😎

SoftwareDeveloperDiaries
Автор

Your channel is very underrated, amazing job.

omaryasser
Автор

This video is surely going to be a life saver for me, Thank you

AdarshNamboothiri
Автор

This video is really helpful, you explained very deeply, thanks a lot!

fatimaiqra
Автор

Useful content with crystal clear explanation

aokaziz
Автор

You are so good with your explanation. Thank you.

paschalynukwuani
Автор

wow this is a great video . I'm curious where did you learn how to use the developer tools for memory and performance ? I haven't used those tabs in my work but would love to do so in the future

darrenpierre
Автор

Excellent and clear explanation, thanks:)

vwcxgye
Автор

Thanks, seems promising, ill try to use what i learned to identify and fix a mem leak at my now with it

criticalthinkergis
Автор

such a great video, I'm looking forward to see more content like this, you got a new sub.

germanmartinezsolis
Автор

a GREAT explanation. thank you so much

Hala-osij
Автор

Wow Thanks a lot. It's what I want to know

qugiidp
Автор

Great information and excellent presentation.

mrkorzj
Автор

Hello, with the setTimeout memory leak. Does no variable ever get garbage collected inside of setTimeout, or is it just references to dom elements that dont get cleaned up. If you had node set = to 10 would it still have been a memory leak?

luck-xcdy
Автор

Great explanation❤❤
Btw what is the tool u r using to draw and write ur explanation?

nttmiwt
Автор

Hey bro! Awesome content. In your third approach you are deleting the property "delete nodes.btn". But "useStrict" doesn't allow us to use "delete". What can be other way to do that?

salmanrana
Автор

Hi i have an issue with my nestjs application even there is no api calls from day 1, the cpu usage is increasing gradually, could you please share any idea how to fix that

sindhu
Автор

great video. What tool are you using for this explanation

Petersonbabs
Автор

Amazing video❤ The fact that it has so less views and engagement makes me kinda sad

itsallsands
Автор

This pretty interesting, but when it comes to determine memory leaks in app like Angular, it very difficult to find it. Because it's huge amount of functions in it, and names like "lj, H9, Xv"... not sure what all those functions comes from.
Do you know how debug memory leaks in TypeScript apps? I believe it's after transpiler comes those names.

MrFikret