memory-debug · git:20260506.478f83b · 2026-05-06 · sha256 40000c496c5d3e6a

memory-debug git:20260506.478f83bA

Immutable. This exact content never changes and is served at /api/v1/blob/40000c496c5d3e6a.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vm56be6ltibfvz6m/40000c496c5d3e6a4fff9a2712253ee4172ad074e1aeae3a142df94a6c7f9322.json

Then /plugin install memory-debug@markdownregistry-vm56be6ltibfvz6m in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: memory-debug
description: Debugging memory leaks, out-of-memory errors, and garbage collection
---

# Memory Debugging Skill

This skill is designed for identifying and resolving memory leaks and excessive memory footprint allocations.

## When to use this skill
- When an application slowly consumes more RAM over time without releasing it (Memory Leak).
- When facing OutOfMemoryError (OOM) crashes.
- When optimizing Garbage Collection (GC) pauses causing latency.

## Guidelines
- **Heap Dumps:** Export and analyze heap dumps or memory snapshots to find retained objects.
- **Closures & Listeners:** In GC languages, look out for un-unregistered event listeners or dangling closures capturing large scopes.
- **Connections:** Ensure database and network connections are gracefully closed.
- **Streaming:** Avoid loading large files or datasets entirely into memory. Use streaming APIs instead.