Memory Leak Debugging

chromedevtools/chrome-devtools-mcpOfficial

This one walks you through finding and fixing memory leaks in JavaScript and Node.js apps. It's opinionated about not reading raw heapsnapshot files directly because they'll blow up your token budget, instead pushing you toward memlab for analysis. The workflow is solid: use chrome-devtools-mcp to capture snapshots at baseline, after triggering the leak, and after cleanup, then let memlab find the leak traces automatically. It includes fallback scripts if memlab isn't available and references for common culprits like detached DOM nodes, uncleaned event listeners, and unbounded caches. Helpful that it reminds you detached DOM nodes aren't always bugs since they're sometimes intentional caches.

skills.sh installs: 3.5K
GitHub stars: 55K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add chromedevtools/chrome-devtools-mcp --skill memory-leak-debugging --agent claude-code

Installs into .claude/skills of the current project.

Files

Memory Leak Debugging

This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools.

Prerequisites

Advanced memory debugging tools (compare_heapsnapshots, get_heapsnapshot_details, etc.) are only available when the server is started with the --memoryDebugging flag. First check if these tools are available; if not, try to read the MCP configuration file to check if --memoryDebugging is enabled.