Loading
Pick a focused question that fits your time, stack, and interview goal.
11 results across 1 active filter
Page 1 of 1
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Connects EF Core change tracking to object retention, query shape, projections, and read-only API performance.
Shows how publisher-to-subscriber references can retain objects and how to clean up event-based lifetimes.
Explains when to capture dumps, what to compare, and how to use roots without turning dumps into guesswork.
Uses file upload processing to practice bounded memory, stream ownership, temporary files, and retained buffers.
Gives a practical incident flow for memory growth using metrics, traffic correlation, heap evidence, and safe mitigation.
Clarifies the difference between objects being retained accidentally and code simply allocating too much temporary memory.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.