openclaw-test-heap-leaks

Diagnose memory leaks in vitest by collecting repeated .heapsnapshot files across test workers and comparing them to identify retained modules. This skill automates delta analysis between snapshots to distinguish transformed-module retention from actual runtime leaks.

Intermittent test memory growth in NodeJS CI lanes is caused by either transformed-module retention or runtime leaks. Comparing repeated heap snapshots from the same PID triangulates the exact source of the memory growth across test workers.

Compare heap snapshots to find retained memory by running the heapsnapshot-delta tool to calculate actionable deltas between before and after states. This isolates whether transformed modules or runtime objects are causing the leak.

You do not need to manually trigger heap snapshot collection for CI diagnostics. The provided lane-based workflows automate the collection of .heapsnapshot files across workers during test execution to produce comparable deltas.

You can use this to triage test performance issues in NodeJS workers by analyzing heap snapshot deltas. It pinpoints memory growth patterns across test lanes to help teams reproduce and resolve intermittent CI test failures.

The best way to distinguish transformed-module retention from runtime leaks is by triangulating repeated heap snapshots from the same PID. The delta analysis tool isolates retained module objects from actual runtime memory leaks.