openclaw-test-heap-leaks

Diagnose memory leaks in a vitest test suite by capturing and comparing repeated .heapsnapshot files to identify retained objects and memory growth. This process uses delta analysis to surface dominant retained objects across test lanes.

OOM scenarios during CI debugging often occur due to memory growth from retained objects or transformed-module retention in shared workers. Analyzing heap snapshot deltas helps identify whether the issue is runtime leaks or module retention.

Capture before and after heap snapshots for memory growth analysis by running a dedicated heap-leak investigation workflow. This automation reproduces memory growth across test lanes and generates snapshot pairs for comparison.

Yes, you can use heap snapshot deltas to triage transformed-module retention versus runtime leaks. The analysis differentiates between retention in shared workers and actual runtime leaks, providing guidance for cleanup or isolation patches.

Automate heap snapshot collection in unit-fast lanes by applying the heapsnapshot-delta.mjs tool to capture repeated .heapsnapshot files. This ensures deterministic snapshot collection and per-PID delta analysis for accurate triaging.

pnpm environments support deterministic snapshot collection for memory leak diagnostics by running the dedicated heap-leak investigation workflow. This setup captures repeated .heapsnapshot files and compares per-PID deltas to identify memory growth.