Memory leak debugging with Chrome DevTools MCP
Find and fix JS/Node memory leaks — capture heap snapshots, compare them, walk retainers and dominators with the MCP memory tools
- What
- Find and fix JS/Node memory leaks — capture heap snapshots, compare them, walk retainers and dominators with the MCP memory tools
- Cost
- Free
- Needs
- the chrome-devtools-mcp server installed and started with the --memoryDebugging flag (advanced memory tools only exist with it); a JS/Node app or web page to investigate — the skill is guidance the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @chromedevtools's memory-leak-debugging skill: expert guidance for finding, diagnosing and fixing memory leaks in JavaScript and Node.js apps using the Chrome DevTools MCP memory tools. Core principles: prefer the MCP memory tools (never read raw `.heapsnapshot` files — they're huge and burn tokens), isolate the leak (browser vs Node), know the common culprits (detached DOM nodes, unhandled closures, globals, unremoved event listeners, unbounded caches), and close loaded snapshots (`close_heapsnapshot`) to release server memory. The workflows: 1) capturing — drive the page with page-scoped tools, repeat interactions 10 times to amplify the leak, snapshot at baseline/target/final states; 2) comparing — summary first with `get_heapsnapshot_summary`, then `compare_heapsnapshots` with detailed class diffs only for suspicious growth; 3) inspecting retainers and dominator chains (`get_heapsnapshot_retainers`, `get_heapsnapshot_retaining_paths`, `get_heapsnapshot_dominators`, duplicate strings); 4) categorized filters (`objectsRetainedByDetachedDomNodes`, `objectsRetainedByEventHandlers`, `objectsRetainedByContexts`, `objectsRetainedByConsole`). Honest caveats: the advanced memory tools only exist when the chrome-devtools-mcp server is started with the `--memoryDebugging` flag; pairs with the `chrome-devtools-cli` listing for driving the browser. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the chrome-devtools-mcp server installed and started with the --memoryDebugging flag (advanced memory tools only exist with it); a JS/Node app or web page to investigate — the skill is guidance the agent follows, not software Install "Memory leak debugging with Chrome DevTools MCP" for me. It gives my agent @chromedevtools's memory-leak workflow: prefer the MCP memory tools over raw .heapsnapshot files, isolate the leak (browser vs Node), capture snapshots at baseline/target/final states (repeating interactions 10x to amplify), compare snapshots with compare_heapsnapshots, walk retainers and dominator chains, use categorized filters (detached DOM nodes, event handlers, contexts, console), and close loaded snapshots afterwards. Pairs with the chrome-devtools-cli skill. Apache-2.0 licensed. Repository: https://github.com/chromedevtools/chrome-devtools-mcp/blob/main/skills/memory-leak-debugging/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "memory-leak-debugging". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. start the chrome-devtools-mcp server with --memoryDebugging; point the agent at the app/page with the suspected leak). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.