~/talk

Memory Don't Forget To Take Out The Garbage

Talkat FFConf 2017 · 2017-11-09..11-10· [javascript, web-performance]
slides:none on file

Explains how JavaScript actually reclaims memory: new objects go into a young generation with minor garbage collection ~1 ms and surviving pages move to an old generation handled by mark‑sweep/compact; marking can pause apps up to ~100 ms so V8 concurrent marking 70–80% reduces pauses. Gives measurable heuristics—Hello World ≈100 MB, JS heap ≈3 KB, crowded page ~500 MB—and shows practical diagnostics and fixes using Chrome DevTools: task manager, performance graphs and memory snapshots to find globals, timers, listeners and detached DOM nodes.

AI-written summary · about

  1. 0:00Introduction
  2. 0:36About Katie
  3. 1:20Memory is important
  4. 3:28What is memory
  5. 5:20Heaps
  6. 5:54Variables
  7. 6:07Memory
  8. 7:12Scopes
  9. 8:39Garbage Collection
  10. 10:40Young Generation
  11. 11:28Pages
  12. 11:48Objects
  13. 14:18Major Garbage Collection
  14. 15:34Performance
  15. 16:38WebAssembly
  16. 17:22Unreal Engine
  17. 18:01Web Assembly
  18. 18:46Memory Problems
  19. 19:49Task Manager
  20. 20:58Hello World
  21. 21:35Minimum need
  22. 22:14Memory leaks
  23. 23:34Accidental Globals
  24. 25:58Event listeners
  25. 26:38orphaned DOM nodes
  26. 27:08memory snapshot
  27. 28:02summary
  28. 28:58stickers
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.