What problem does it solve? JavaScript and Node.js applications that grow in memory until they hit OOM errors are hard to debug because raw heap snapshots are too large to inspect directly. This Skill provides a structured workflow for capturing, comparing, and analyzing heap snapshots with Chrome DevTools MCP memory tools to pinpoint the exact objects and retaining paths causing leaks. ## Core Features & Use Cases - Snapshot Capture and Comparison: Take baseline, target, and final heap snapshots while interacting with a page, then diff them with compare_heapsnapshots to find growing object classes. - Retainer Inspection: Trace why suspicious objects stay reachable using retainer, retaining-path, dominator, and edge queries before changing any code. - Fallback Analysis: Use memlab or the included compare_snapshots.js Node.js script when built-in MCP tools are insufficient. - Use Case: A user reports that their React app's memory climbs after repeatedly opening and closing a modal. The Skill guides capturing snapshots around the interaction, identifying detached DOM nodes in the diff, and tracing the retaining event listener back to the component code. ## Quick Start Ask the agent to investigate high memory usage in your web app by capturing and comparing heap snapshots with Chrome DevTools MCP.
