How do you debug a memory leak in Chrome DevTools for a SPA?
PICTURE THIS: ARRAY IN MEMORY
Index starts at 0. Scan once for max — O(n).
Simple meaning
I take heap snapshots before and after visiting a route twice and look for detached DOM nodes or growing arrays.
WHY — Browser instead of guessing?
Why interviewers care about Browser:
question about Browser.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1I take heap snapshots
before and after visiting a route twice and look for detached DOM nodes or growing arrays.
- 2Allocation instrumentation shows what
retains the objects.
- 3Typical leaks are uncleared
intervals, global caches, and listeners on window.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
I take heap snapshots before and after visiting a route twice and look for detached DOM nodes or growing arrays. Allocation instrumentation shows what retains the objects.