openclaw-test-heap-leaks

To identify memory leaks in vitest test runs, collect repeated .heapsnapshot files during execution and use delta analysis to compute memory growth patterns. This separates transformed-module retention from actual runtime leaks by comparing snapshot deltas across different PIDs.

RSS increases during node testing due to module retention or runtime leaks. Triage RSS increases by collecting multiple .heapsnapshot files and calculating deltas with the heapsnapshot-delta.mjs script to isolate whether transformed modules or actual runtime hotspots cause the growth.

Reproduce flaky CI test lanes by applying memory-diagnostic workflows locally and in CI to trigger memory growth. Collect multiple .heapsnapshot files from the failing lanes and compare deltas across PIDs to isolate the specific hotspot tests causing the flakiness.

Yes, you can use pnpm to run the memory-diagnostics workflow that generates heap snapshots. By computing deltas across collected .heapsnapshot files from different PIDs, you can distinguish transformed-module retention from genuine runtime leaks in your test environment.

Heap snapshot delta analysis works for both local development and CI environments. The scripts/heapsnapshot-delta.mjs tool computes deltas and presents actionable findings to triage RSS increases and isolate hotspot tests regardless of where the memory growth occurs.

Heap snapshots may not be suitable when you need immediate feedback on memory growth without the overhead of generating and storing multiple .heapsnapshot files. If the leaks are easily reproducible through simpler profiling methods, the delta analysis workflow might be unnecessary for your testing setup.