openclaw-test-heap-leaks

To diagnose memory leaks and heap growth in vitest test runs, compare heap snapshots to identify dominant object families. This process surfaces runtime objects or transformed module retention driving memory spikes during unit-fast and batch lanes.

OOM errors during pnpm test suites often stem from unchecked memory growth in shared workers. Analyzing heap snapshot deltas helps identify whether transformed module retention or runtime objects cause the memory exhaustion.

You compare heap snapshots to find dominant retainers by running the heapsnapshot-delta.mjs script between two test states. This script computes deltas to reveal specific object families retaining memory and causing growth.

The best way to reproduce and triage memory spikes locally is by enforcing reproducible steps to trigger the failure shape. Collecting and comparing heap snapshots then isolates the exact module or runtime object causing the leak.

Yes, heap snapshot analysis applies directly to Linux CI-style test failures. It guides targeted fixes by focusing on unit-fast and batch lanes to surface dominant retainers causing heap-related failures in automated environments.

Heap delta analysis works for detecting memory leaks in shared workers by identifying transformed module retention. It distinguishes between shared worker module retention and standard runtime objects to guide targeted fixes.