profile-memory

Profile Sidecar memory usage and detect leaks with Go pprof and heap analysis.

1.0k|79|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/marcus/sidecar --skill profile-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile-memory
Source: https://github.com/marcus/sidecar/tree/main/.claude/skills/profile-memory
Command: npx skills add https://github.com/marcus/sidecar --skill profile-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory profiling in Sidecar can be complex and time-consuming, especially when hunting leaks and performance regressions.

Core Features & Use Cases

  • Memory profiling via Go pprof, system tools, and heap analysis to identify leaks (memory, goroutines, file descriptors), CPU profiling, and unresponsive plugins.
  • Triaging symptoms with recommended tooling and manual checks for RSS, FD counts, and heap growth.
  • Use Cases: diagnose memory leaks in Sidecar, analyze performance hotspots, verify fixes in CI by repeated profiling.

Quick Start

Run a memory profiling session against the running Sidecar process using pprof, vmmap/vmstat, and lsof to identify leaks.

Frequently Asked Questions about profile-memory

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

FAQPage Schema
How do I detect memory leaks in a Sidecar process using Go pprof?

Detect memory leaks in a Sidecar process by running a profiling session with Go pprof, analyzing heap growth, and monitoring RSS via system tools to isolate memory regressions.

What is the best way to triage unresponsive plugins and goroutine leaks?

Triage unresponsive plugins and goroutine leaks by profiling goroutine growth and file descriptor counts using pprof and system tools like lsof to identify resource exhaustion.

Can I run memory profiling for Sidecar in a production environment?

You can run memory profiling for Sidecar across development, staging, or production environments to diagnose memory issues and identify performance hotspots safely.

Do I need Go tooling installed to diagnose RSS and heap growth?

Yes, diagnosing RSS and heap growth requires Go tooling, specifically pprof, alongside system tools like vmmap or vmstat to perform manual checks and triage symptoms.

Why does Sidecar memory usage keep growing and how do I isolate the regression?

Sidecar memory usage grows due to leaks in memory, goroutines, or file descriptors; isolate the regression by applying heap analysis and CPU profiling during repeated CI runs.