openclaw-test-heap-leaks
Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.
Best for CI pipeline debuggingWorks with GitHub
⌘source
- author
@openclaw- language
- TypeScript
★360kstars
73kforks
Apr 17, 2026
✦overview.md
Key Features
- ·Investigates memory growth in pnpm test runs
- ·Collects and compares heap snapshot files
- ·Triages transformed-module retention vs runtime leaks
- ·Patches cleanup logic or isolates hotspot tests
- ·Uses memory trace environment variables for RSS summaries
Use Cases
- →Reproducing test-lane memory growth in CI environments
- →Investigating Vitest worker out-of-memory (OOM) errors
- →Analyzing suspicious resident set size (RSS) increases during OpenClaw testing
Best for
- ✓CI pipeline debugging
- ✓Performance investigation teams
- ✓Test infrastructure maintenance
Not ideal for
- !One-off script analysis
- !Production application monitoring
- !Non-OpenClaw projects
FAQs
name
openclaw-test-heap-leaks
description
Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.
OpenClaw Test Heap Leaks
Use this skill for test-memory investigations. Do not guess from RSS alone when heap snapshots are available. Treat snapshot-name deltas as triage evidence, not proof, until retainers or dominators support the call.
Workflow
-
Reproduce the failing shape first.
- Match the real entrypoint if possible. For Linux CI-style unit failures, start with:
pnpm canvas:a2ui:bundle && OPENCLAW_TEST_MEMORY_TRACE=1 OPENCLAW_TEST_HEAPSNAPSHOT_INTERVAL_MS=60000 OPENCLAW_TEST_HEAPSNAPSHOT_DIR=.tmp/heapsnap OPENCLAW_TEST_WORKERS=2 OPENCLAW_TEST_MAX_OLD_SPACE_SIZE_MB=6144 pnpm test- Keep
OPENCLAW_TEST_MEMORY_TRACE=1enabled so the wrapper prints per-file RSS summaries alongside the snapshots. - If the report is about a specific shard or worker budget, preserve that shape.
- Before you analyze snapshots, identify the real lane names from
[test-parallel] start ...lines orpnpm test --plan. Do not assume a singleunit-fastlane; local plans often split intounit-fast-batch-*.
-
Wait for repeated snapshots before concluding anything.
- Take at least two intervals from the same lane.
$install
1-click copynpx skills add openclaw/openclaw --skill openclaw-test-heap-leaksSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.