memory-leak-debugging
π―SkillHelps find and fix memory leaks in JavaScript and Node.js apps, where an app keeps using more and more memory. It uses Chrome DevTools tools to take and compare memory snapshots and find what is holding on to memory.
Installation
npx skills add chromedevtools/chrome-devtools-mcp --skill memory-leak-debuggingRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/memory-leak-debuggingInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/memory-leak-debugging/ - All projects
~/.claude/skills/memory-leak-debugging/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View on GitHub βDiagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.
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.
Core Principles
- Prefer MCP memory tools: Do NOT attempt to read raw
.heapsnapshotfiles directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots. - Isolate the Leak: Determine if the leak is in the browser (client-side) or Node.js (server-side).
- Common Culprits: Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded. Note: Detached DOM nodes are sometimes intentional caches; always ask the user before nulling them.
- Close Loaded Snapshots: Heap snapshots can be large. After completing an investigation, use
close_heapsnapshotfor each loaded snapshot to release memory held by the MCP server.
Workflows
1. Capturing Snapshots
When investigating a frontend web application memory leak, utilize the chrome-devtools-mcp tools to interact with the application and take snapshots.
- Use page-scoped tools like
click,navigate_page,fill, etc. (specifyingpageId) to manipulate the page into the desired state. - Revert the page back to the original state after interactions to see if memory is released.
- Repeat the same user interactions 10 times to amplify the leak.
- Use
take_heapsnapshot(withpageId) to save.heapsnapshotfiles to disk at baseline, target (after actions), and final (after reverting actions) states.
2. Comparing Snapshots
Once you have generated .heapsnapshot files using take_heapsnapshot, compare them with Chrome DevTools MCP memory tools.
- Start with
get_heapsnapshot_summaryfor each snapshot to confirm that the files load and to compare high-level totals. - Use
compare_heapsnapshotsto compare baseline and target snapshots. Start withoutclassIndexfor the summary diff, then request detailed class diffs only for suspicious growth by specifyingclassIndex. - Use the summary output from
compare_heapsnapshotsbefore drilling into specific node IDs.
3. Inspecting Retainers and Dominator Chains
When a class or object type grows unexpectedly, inspect the retaining chain and dominators with the MCP tools before changing code.
- Use
get_heapsnapshot_class_nodesto list instances of the suspicious class. - Use
get_heapsnapshot_retainers,get_heapsnapshot_retaining_paths,get_heapsnapshot_dominators, andget_heapsnapshot_edgesto understand why representative nodes are still reachable. - Use
get_heapsnapshot_object_detailswith a specificnodeIdto retrieve detailed object metadata (size, type, distance, and DOM detachedness). - Use
get_heapsnapshot_duplicate_stringswhen string growth dominates the diff. - Read references/common-leaks.md for examples of common memory leaks and how to fix them after the retaining path points at application code.
4. Advanced Analysis and Categorized Filters
Use built-in MCP memory tools and filters to pinpoint specific leak categories directly without external tools.
- Use
get_heapsnapshot_detailsorget_heapsnapshot_class_nodeswithfilterNameto target common leak causes:objectsRetainedByDetachedDomNodes: Identifies detached DOM elements retained in memory.objectsRetainedByEventHandlers: Identifies objects kept alive by unremoved event listeners.objectsRetainedByContexts: Identifies objects trapped in closures or execution contexts.objectsRetainedByConsole: Identifies objects retained by console logging.
More from this repository8
Lets your AI coding tool open and control a real Chrome browser. It can test pages, find bugs, take screenshots, and check how fast a site loads.
Chrome DevTools for coding agents
Chrome DevTools MCP is an official MCP server from the Chrome DevTools team that lets AI coding agents control and inspect a live Chrome browser.
Lets your AI agent control and inspect a Chrome browser to debug web pages. It can open pages, click and fill in forms, take screenshots, check page speed, read styles, and watch network traffic, through the chrome-devtools-mcp tool.
Helps you find out why the main content of a web page appears slowly, and how to fix it. It uses Chrome DevTools tools to record a page load, measure each stage and point to the slowest part.
Lets you control the Chrome browser from your terminal with simple commands. You can open pages, click, type into forms and take page snapshots, or put these steps in shell scripts to automate browser tasks.
Helps find and fix accessibility problems on web pages, so people using screen readers or keyboards can use them. It drives a Chrome browser to run audits and check labels, focus, color contrast and tap target size.
Helps fix setup problems when your AI assistant cannot connect to Chrome through Chrome DevTools MCP, a tool that lets AI control the browser. It reads your config file, matches common error messages and walks you through fixes step by step.