Plugging Memory Leaks With The Chrome Dev Tools - Ben Dilts
Why Stack Overflow recommends it
Stack Overflow users link it when asking or answering how to track down memory leaks in web apps with Chrome DevTools, including Vue, Angular and Electron apps.
Recommended by 1 people across 1 different months, 2020 to 2022.
What it is
A 52-minute conference talk from UtahJS 2017 in which Ben Dilts shows how to use Chrome DevTools to find JavaScript memory leaks, cut time spent in garbage collection, and lower overall memory use. It argues that garbage collection alone does not protect apps from leaks.
What people said
Recommends Awesom-o · 2020-12 · Stack Overflow · on “Vue project slows down more after every route”
Oke, so i've kind of solved it for now. I'm still new to all this, but i started to look more into working with dev tools so i can find out where issues like this come from. I think i still can win a lot with this, but for now it helped to destroy my PIXI app from data when i'm done with it. beforeDestroy () { this.app.destroy() } Maybe some usefull links if someone ever finds this thread that has similar issues: Using dev tools to find memory leaks: [this video] [LINK] Avoiding memory leaks in vue: [LINK]
Cites Avner Moshkovitz · 2020-01 · Stack Overflow · on “Getting an "out of memory" error in Javascript”
I have a webapp with many (1000) buttons. Each button reads an image (4032x3024 ~1.5MB - high resolution is needed) from a webserver when being clicked. When running on a phone (Android Pixel3), after multiple clicks, when clicking on a button that was not clicked before, results in an error: net::ERR_OUT_OF_MEMORY when getting the image from the webserver. I tried 2 use cases: Use case1 - previously read images are released before loading the next image. In this case I don't see the out-of-memory problem but the user experience is poor, because each image is retrieved from the webserver regardless if it has been read before. Use case2 - previously read images are not released. In this case
Cites rodent_la · 2022-04 · Stack Overflow · on “Angular: Is the console.log() an object cause the memory leak?”
As electron angular application increases memory usage over time and I am trying to find the leak. So I studied to debug memory leaks with chrome dev tools and came across this video presentation. [this video] [LINK] I am quite confused about this statement of console log (or debug, info) an object cause memory leak. As our application dump a lot of log and it seems increasing memory usage. We did need to dump log. Is there any difference between dumping object or object convert to JSON.stringify(object)? String is also a kind of object, right?