detect-ssr-leak

Detect server-side memory leaks in Node.js SSR applications via RSS and heap analysis.

970|131|Updated Jan 14, 2018
One-click install
npx skills add https://github.com/cabloy/cabloy --skill detect-ssr-leak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-ssr-leak
Source: https://github.com/cabloy/cabloy/tree/main/vona/.claude/skills/detect-ssr-leak
Command: npx skills add https://github.com/cabloy/cabloy --skill detect-ssr-leak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ws, and includes scripts (resource) components.

What problem does it solve?

This Skill helps identify growing memory usage and server-side memory leaks in Node.js SSR applications by providing a structured diagnostic workflow instead of relying on guesswork.

Core Features & Use Cases

  • Memory Leak Detection Workflow: Measures RSS growth, heap usage, V8 contexts, and heap snapshots across multiple diagnostic phases.
  • Root Cause Analysis: Compares CDP heap snapshots to identify leaking object types such as retained closures, objects, strings, and arrays.
  • Use Case: Diagnose a Vue or React SSR service whose memory consumption increases after repeated requests and generate evidence-based recommendations for fixing the underlying issue.

Quick Start

Use the detect-ssr-leak skill to analyze my Node.js SSR service for memory leaks using the target URL I provide.

Frequently Asked Questions about detect-ssr-leak

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a memory leak in a Node.js SSR application?

To find a memory leak in a Node.js SSR application, you measure RSS growth, instrument heap usage, and compare V8 heap snapshots to identify retained closures, objects, strings, and arrays causing memory consumption to increase after repeated requests.

Why does my Vue or React SSR service have increasing memory usage after repeated requests?

Increasing memory usage in Vue or React SSR services typically indicates server-side memory leaks from retained objects or closures that the garbage collector cannot release, requiring heap snapshot analysis to diagnose the exact leaking object types.

What is the best way to analyze V8 heap snapshots for Node.js memory leaks?

The best way to analyze V8 heap snapshots for Node.js memory leaks is using CDP heap snapshot instrumentation to compare retained objects across diagnostic phases, identifying specific closures, strings, and arrays responsible for heap growth.

Can I diagnose SSR memory leaks using external RSS monitoring and heap instrumentation?

Yes, you can diagnose SSR memory leaks by combining external RSS monitoring with V8 heap instrumentation to measure heap growth, compare retained objects, and identify probable leak sources through a structured diagnostic workflow.

Do I need WebSocket connections to run Node.js SSR memory leak diagnostics?

Yes, WebSocket connections are required as a dependency to facilitate V8 inspection workflows and communication between the diagnostic scripts and the Node.js SSR service during heap snapshot analysis.