openclaw-test-heap-leaks

You can identify test memory leaks by comparing multiple heap snapshots taken across pnpm test runs to isolate dominant object families and distinguish actual runtime leaks from retained transformed-module growth.

Identifying heap snapshot deltas involves loading and parsing repeated .heapsnapshot files from parallel workers to compare memory growth and report dominant object families within unit-fast or batch lanes.

Increasing RSS during repeated pnpm test invocations often indicates memory leaks in the test suite, which you can triage by analyzing heap snapshots to distinguish retained module growth from actual runtime leaks.

Distinguishing transformed-module retention from runtime leaks requires analyzing heap snapshot deltas across test lanes to identify whether memory growth stems from retained modules or actual runtime object accumulation.

Yes, you can use heap snapshots to triage memory growth in parallel node test runs by collecting and comparing repeated .heapsnapshot files across workers to guide isolation or cleanup patches.

Heap snapshot performance analysis requires collecting multiple snapshots across repeated test runs to identify deltas, making it limited by the overhead of snapshot generation and parsing during parallel pnpm test execution.