What is a memory leak in a garbage-collected language?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
The GC frees unreachable objects, but event handlers, static caches, and forgotten subscriptions keep objects reachable.
WHY — Memory instead of guessing?
Why interviewers care about Memory:
who only read docs from people who shipped.
and tied to .NET work.
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:
- 1The GC frees unreachable
objects, but event handlers, static caches, and forgotten subscriptions keep objects reachable.
- 2That looks like a
leak even though the GC is working.
- 3I unsubscribe and use
WeakEvent or IDisposable on publishers.
- 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
The GC frees unreachable objects, but event handlers, static caches, and forgotten subscriptions keep objects reachable. That looks like a leak even though the GC is working.