openclaw-test-heap-leaks

To diagnose memory leaks in vitest workers, capture and compare heap snapshots across pnpm test runs to identify dominant leak sources by PID. This skill computes snapshot deltas to reveal whether growth stems from transformed-module retention or runtime objects.

Worker OOMs and RSS spikes in CI testing pipelines occur when test workers exhibit unmanaged memory growth. Comparing heap snapshots between test runs isolates the dominant leak sources, allowing you to triage retention issues and propose targeted fixes.

You compare heap snapshots by collecting before and after snapshots for the same PID and computing the deltas. The script reports the top memory differences, optionally filtered by lane and PID with configurable thresholds.

Yes, you can configure memory leak thresholds for specific pnpm test workers. The heap snapshot delta script computes memory growth and reports top differences with configurable thresholds, optionally segmented by lane and PID.

Yes, this heap snapshot approach works for both CI pipelines and local development. It captures and aggregates snapshots from parallel test workers to identify memory growth and RSS spikes wherever pnpm test runs execute.

Triaging growth between transformed-module retention and runtime objects matters because it pinpoints the exact mechanism causing memory leaks. This distinction allows you to propose targeted fixes for the specific module or object retention issue.