Memory Leak Detector Skill for Browser Event Cleanup

Inspect event registration and cleanup in a local component, then compare retained work after repeated mount cycles.

Install in Claude Code

Use your local app, browser DevTools, and a dialog that can be opened and closed repeatedly.

Get the complete `plugins/performance/memory-leak-detector/skills/detecting-memory-leaks` directory from the pinned GitHub commit.
Copy it into the target project's `.claude/skills/`. Check `.claude/skills/detecting-memory-leaks/SKILL.md`, start Claude Code at the project root, and call `/detecting-memory-leaks`.

Example task

Open and close a local dialog with a resize handler 20 times. Trigger one resize and check whether handlers from prior dialogs still run. Add cleanup and repeat.

What to check

Closed dialogs no longer receive resize callbacks. The repeated sequence reveals whether listeners continue to accumulate.

Original SKILL.md on GitHub · Updated 2026-11-13

Frequently asked question

Does a single increase in memory prove a leak?

Repeat the same operation under comparable conditions and inspect which objects remain retained.