Finding memory leaks using Chrome Dev Tools

[@deepakp4169]

Thank you!
This was very short and precise!!

[@anj000]

If it really was that simple...
In reality you click on the spike, and have literally hundred of items, almost none of them are detached. And if you find one detached it takes up like 0,01%, and it anyway leads to the internal code of the library you are using.

[@ProfesorCafe]

Hey if anyone in this comment section is as dumb as me (kudos for that) and thinks the graphs on 0:00 and 4:19 look kinda the same and no progress was made, please check the scale thingy on the left of the graph that says 10.2kb on 0:00 and 100b on 4:19 instead of the length of the bar-thingies.
I know it may look obvious, but I'm a recovering crayon eating addict, so maybe it helps any of you. Also thanks for the video Mitchel it was very helpful.

[@MelUgaddan]

Thank you for this ! it's very short and simple

[@dpk7119]

if we got html detached buttons count after performing action, can we consider them as memory leaks

[@Muyiwamighty]

Wow this is awesome...u got one more subscriber, please keep it up with videos like this. Very used

[@Muyiwamighty]

Useful*

[@sofianealloui]

the deep side of youtube:

[@messili4524]

Awesome!!

[@Sangeeta1616]

thanks a lot -- for clearing it in simple way !!

[@mohammadnoushadsiddiqi66]

Thanks that was helpful

[@kriscollins1541]

thank you, that was really helpful

[@Shuyinz]

Very useful! Thanks!

[@mitchelsoltys7069]

Glad it was helpful!

[@kag3670]

Thank you for sharing 👍

[@antio1753]

JS Frameworks solve this problem ??

[@mitchelsoltys7069]

Frameworks help organize code, but leaks can occur with any code under various conditions.