The memory hierarchy from CPU registers and cache to main memory is the foundation for understanding how applications store and access data.
The JavaScript engine compiles code into an abstract syntax tree and bytecode, then allocates memory for variables on the heap, which is managed in structures like arenas and zones.
The garbage collector automatically frees memory by tracking object references, and an object is only collected once it is no longer referenced by any part of the application.
Four common memory leak patterns in JavaScript include unterminated closures, leaky timers, detached DOM nodes with active listeners, and unbounded global caches.
A variety of tools, including Chrome DevTools Memory and Performance tabs, framework-specific dev tools, and system monitors like htop, can help diagnose memory consumption issues.
The first step in fixing the application's memory leak was to prevent unnecessary re-renders by comparing incoming data with existing data before updating the UI.
Two separate memory leaks were traced to third-party UI libraries where component instances and their templates were not being properly destroyed, leading to cumulative memory growth.
Jobs that call for the skills explored in this talk.