kova-test-heap-leaks

Diagnose Vitest heap growth by capturing repeated heap snapshots across worker lanes and running a delta comparison script to identify dominant self-size entries for triage. This distinguishes real cleanup bugs from snapshot noise or retained module graphs.

RSS spikes are insufficient for memory leak triage because they lack the granularity to distinguish true cleanup bugs from shared-worker retained module graphs. Heap snapshot metadata provides retained object families and dominator evidence needed for accurate diagnosis.

Compare heap snapshots by running the heapsnapshot-delta.mjs script against two snapshot files, or let it automatically select the earliest and latest snapshots per PID in a lane directory to classify growth patterns like transformed-module retention versus lifecycle leaks.

Yes, you can triage memory leaks in pnpm-based Vitest projects by enabling KOVA_TEST_MEMORY_TRACE for scheduled heap snapshot collection, then comparing snapshot deltas to validate conclusions using retainers and dominators for actionable fixes.

The best way to fix suspected memory leaks is to translate dominant heap snapshot evidence into concrete next steps such as lane isolation, hotspot updates, singleton isolation, or test and runtime cleanup patches based on the identified growth patterns.

You should not use heap snapshot deltas for test OOM debugging when you cannot select the real test-parallel lane or PID shape, as accurate triage requires capturing repeated snapshots from the correct worker lane directory.