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

My Angular course: https://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: https://youtu.be/ulWEJaLgqNM Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076 My game dev channel: https://www.youtube.com/@joshmoronypixels MY GEAR: Keyboard: https://adm42.dev/?ref=3 Neovim setup: https://github.com/joshuamorony/lazyvim/ Animations: https://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: https://modernangular.com