superbyte-test-heap-leaks

Analyze heap snapshot deltas to triage SuperByte test memory leaks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/qkal/superbyte --skill superbyte-test-heap-leaks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superbyte-test-heap-leaks
Source: https://github.com/qkal/superbyte/tree/main/.agents/skills/superbyte-test-heap-leaks
Command: npx skills add https://github.com/qkal/superbyte --skill superbyte-test-heap-leaks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Investigate and triage memory leaks in SuperByte's test suite by analyzing heap snapshots and RSS growth.

Core Features & Use Cases

  • Reproduce failing shapes in CI and local environments to observe memory behavior during pnpm test runs.
  • Compare successive heap snapshots across lanes or workers to identify retained objects or dominators.
  • Classify growth into retained module graphs or runtime objects and guide remediation efforts.

Quick Start

Reproduce a failing test run with heap tracing enabled and review two consecutive snapshots to identify deltas.

Frequently Asked Questions about superbyte-test-heap-leaks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose memory leaks in a vitest test suite using heap snapshots?

Diagnose memory leaks by comparing consecutive heap snapshots from pnpm test runs to identify retained objects and calculate dominant delta types for remediation.

What causes RSS spikes and OOMs during pnpm test execution?

RSS spikes and OOMs during pnpm test execution are caused by retained module graphs or runtime objects, identified by comparing successive heap snapshots across workers.

Can I compare heap snapshots across different workers or lanes in vitest?

Yes, you can compare heap snapshots across different lanes or workers by parsing snapshot JSON to calculate deltas and classify memory growth into retained module graphs or runtime objects.

What is the best way to triage heap growth in Linux CI environments?

The best way to triage heap growth in Linux CI environments is to reproduce failing test shapes with heap tracing enabled, then review consecutive snapshots to identify dominant delta types.

How do I parse heap snapshot JSON to identify retained dominators in vitest?

Parse heap snapshot JSON by comparing successive snapshots across test sequences to identify retained dominators and report dominant delta types, classifying growth into module graphs or runtime objects.

Does this approach require heap tracing enabled to reproduce failing test runs?

Yes, reproducing failing shapes to observe memory behavior during pnpm test runs requires heap tracing enabled to generate the snapshots needed for delta calculations and remediation guidance.