openclaw-test-heap-leaks

To find memory leaks in a test suite, analyze heap snapshot deltas to identify growing objects and surface retained object families between runs. This approach triages whether growth stems from leaked runtime objects or module retention.

Test suite memory growth often indicates potential leaks that require heap snapshot analysis to diagnose. Comparing before and after snapshots surfaces dominant retained objects and dominators to classify the leak source.

Cross-PID heap snapshot comparisons triage memory deltas by analyzing retained objects and dominators across different processes. You need at least two snapshots per PID and a delta utility to surface the growing object families.

Yes, you can diagnose memory leaks in a Linux CI environment by enabling heap snapshots during test runs and comparing them. This identifies growing object counts and retained runtime objects specific to CI-style unit failures.

Analyzing heap snapshot deltas requires at least two snapshots per PID, the heapsnapshot-delta utility, and the ability to surface retained objects and dominators to classify leaks. Run tests with snapshots enabled to generate the data.