memory-leak-debugging

memory-leak-debugging is an agent skill for finding, diagnosing and fixing memory leaks in JavaScript and Node.js applications. It is for cases where a user reports high memory use or out-of-memory errors, or wants to capture and compare heap snapshots. It uses the Chrome DevTools MCP heap snapshot tools, which summarize, compare and inspect snapshots, so the agent does not have to read the very large raw snapshot files. The advanced memory tools, such as comparing snapshots and reading their details, are only available when the server is started with the memory debugging flag, and the skill checks for that before it begins. The skill first decides whether the leak is in the browser or in the Node.js server. It looks for common culprits such as detached DOM nodes, unhandled closures, global variables, event listeners that are never removed, and caches that grow without limit. It asks before clearing detached DOM nodes, because some are kept on purpose as caches. After an investigation, it closes each loaded snapshot to free memory in the server. It is published in the chromedevtools/chrome-devtools-mcp repository, which has about 53,600 stars on GitHub.…