~/talk

Analyze the JS Heap and Detect Memory Leaks

Talkat NG Belgrade Conf 2026 · on Thursday, 2026-05-07· [javascript, web-performance]
slides:none on file

Browser tabs crash when repeated allocations never free memory; Chrome DevTools let you find why by using the Performance Monitor for live JavaScript heap, DOM node and event-listener trends and the Memory Tab to force GC, take snapshots and inspect retained vs shallow sizes. Common culprits are console.log leaks, forgotten intervals/subscriptions or event listeners and large structures (example: a demo creates 10,000 items and a real case shows DOM nodes growing from 10,000 -> 84,000), and searching snapshots for “detached” often points to the retaining reference.

AI-written summary · about

~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.