The Memory Leak Brain Drain

on YouTube ↗05m

" summary

Shows that the usual culprits are concrete and actionable: turn off the console API because console logs retain objects, unsubscribe long-lived observables to avoid retained subscriptions, and use Chrome DevTools Timeline and Heap snapshots plus the Allocation Timeline to pinpoint when memory climbs and which component or event causes it, reproduce the leak by mimicking long-running users, isolate with a minimal app around a suspect third‑party, and consider upgrade to Angular 4 to avoid common mistakes.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:20What is a memory leak?
3. 0:34Why should you care?
4. 0:58Two Types of Memory Leaks
5. 2:10Timeline View
6. 3:15Heap snapshots
7. 3:25Outside of the tools

" related talks

• 19mTuning Your Angular ApplicationBonnie Brennan, Matt Carniatto · ngVikings 2019
• 03mObservable trapped me in memory leakMaciej Treder · NG Poland 2018
• 09mCommon Angular GotchasYew Hong Tat · NG-MY 2019
• 34mBad Practices, how you should NOT do in Angular worldValentin Kononov · DevFest Gorky 2019
• 41mHow to Improve Angular 2 Performance?Aleksandr Tryshchenko · JavaScript fwdays'17
• 26mProfiling Angular apps like a SharkGil Fink · AngularConnect 2019
• 35mBad Practices, what NOT to do in AngularValentin Kononov · ngVikings 2019
• 41mThe most infamous code smells in Angular ApplicationsJuan Herrera · International JavaScript Conference Munich 2019