What problem does it solve? Test suites running under Vitest can hit out-of-memory failures and unexplained RSS growth, and guessing from RSS alone often misidentifies the cause. This Skill provides a structured workflow to reproduce the failing test shape, capture repeated heap snapshots per worker PID, and classify whether growth comes from retained transformed modules or genuine application object leaks. ## Core Features & Use Cases - Heap Snapshot Diffing: Compare two .heapsnapshot files directly or auto-select the earliest/latest pair per PID within a lane directory using the bundled heapsnapshot-delta.mjs script. - Leak Classification Heuristics: Distinguish retained Vite/Vitest transformed-module growth from real lifecycle leaks involving caches, timers, DB handles, or listeners. - Fix Guidance: Apply timing-driven scheduling fixes, singletonIsolated lane peeling, or targeted cleanup patches, then verify with snapshot re-runs or RSS trends. - Use Case: A CI unit-test lane OOMs at 6GB. You reproduce it with heap snapshots enabled, diff snapshots per PID, find transformed-module retention dominates, and peel the hotspot file into an isolated lane. ## Quick Start Ask the agent to investigate the Vitest test memory growth by reproducing the failing lane with heap snapshots enabled and diffing the snapshots with the heapsnapshot-delta script.
