Hey! Been there. The "(closure)" stuff usually means functions holding onto stuff they shouldn’t. Try filtering for "detached" in the heap snapshot JavaScript view—it’ll highlight DOM nodes that aren’t in the page but still in memory.
For comparing snapshots, Chrome’s "Comparison" mode is clutch. Take one before and after an action to see what’s leaking.
And yeah, your app’s probably not *that* messy... but memory leaks are sneaky!
For comparing snapshots, Chrome’s "Comparison" mode is clutch. Take one before and after an action to see what’s leaking.
And yeah, your app’s probably not *that* messy... but memory leaks are sneaky!