Tracking down a performance (not memory) leak in JavaScript @JoshuaMorony
Tracking down a performance (not memory) leak in JavaScript  @JoshuaMorony
Uploaded March 2025 | Updated September 2026, 2 weeks ago
My Angular course: angularstart.com

This video focuses on how to use the "Bottom-up" section of Chrome DevTools to track down a "processing leak" or "CPU leak"

Previous video: youtu.be/ulWEJaLgqNM

Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076

My game dev channel: youtube.com/@joshmoronypixels

MY GEAR:
Keyboard: https://adm42.dev/?ref=3
Neovim setup: github.com/joshuamorony/lazyvim
Animations: motioncanvas.io

0:00 Memory leak vs CPU leak
1:35 Using Bottom-up in Chrome
4:17 The problem
5:03 The solution

#angular #javascript

- More tutorials: modernangular.com
Tracking down a performance (not memory) leak in JavaScriptWatch this BEFORE updating to signal inputs in AngularWhy you should try to solve challenging JavaScript problems yourselfWhy signal INPUTS in Angular are such a big dealDont use effects/dont subscribe (its the same advice)How Nx fixed my Cloudflare development workflowFull development workflow with neovim on my phoneI created the perfect playground for AngularI built my startup with Angular... RMC Devlog #1I could remove ALL RxJS in my Angular app, but should I?Why XState and RxJS are not too complexEvery uncommon TypeScript concept that is useful to me
Joshua Morony |

Tracking down a "performance" (not memory) leak in JavaScript

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER