Memory Leak Debugging
Skill Verified ActiveDiagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to analyze heapsnapshots or run memory leak detection tools like memlab.
To empower developers to efficiently find and resolve memory leaks in their JavaScript and Node.js applications, improving performance and stability.
Features
- Diagnose memory leaks in JavaScript/Node.js
- Analyze heap snapshots using memlab
- Identify common leak culprits (closures, listeners, DOM)
- Capture browser/Node.js memory snapshots
- Provide guidance on fixing leaks
Use Cases
- When users report high memory usage or OOM errors.
- When needing to analyze heap snapshots for memory leaks.
- When running memory leak detection tools like memlab.
- When investigating detached DOM nodes or unclosed event listeners.
Non-Goals
- Directly reading raw `.heapsnapshot` files.
- Fixing leaks without user confirmation for potential intentional caches (e.g., detached DOM nodes).
- Performing actions outside of memory leak diagnostics and resolution.
Practices
- Code Quality
- Debugging
- Performance Analysis
Prerequisites
- Node.js v20.19+ or newer maintenance LTS
- Chrome current stable version or newer
- npm
- chrome-devtools-mcp installed and configured
Compliance
- info:Telemetry opt-inThe README mentions usage statistics collection is enabled by default and can be opted out with a flag, but does not detail the specific fields collected or provide a schema.
Installation
First, add the marketplace
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp/plugin install chrome-devtools-mcp@chrome-devtools-pluginsQuality Score
VerifiedTrust Signals
Similar Extensions
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Ctx Doctor
100Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes