leak-debugging

Identify and triage handle, memory, and GC leaks in Skyline tests.

17|2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ProteoWizard/pwiz-ai --skill leak-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leak-debugging
Source: https://github.com/ProteoWizard/pwiz-ai/tree/main/claude/skills/leak-debugging
Command: npx skills add https://github.com/ProteoWizard/pwiz-ai --skill leak-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leak debugging helps engineers identify and triage handle leaks, memory leaks, and GC leaks that surface in Skyline tests, guiding profiling and retention-path analysis to enable reliable fixes.

Core Features & Use Cases

  • Step-by-step leak investigation workflows for handle leaks, memory leaks, and GC leaks.
  • Guidance on using dotMemory profiling and GC leak tracking to identify retention paths.
  • Real-world scenarios including nightly tests and CI runs where leaks are observed.

Quick Start

Run the guided leak-investigation workflow on a failing Skyline test to identify retention paths and stabilize tests.

Frequently Asked Questions about leak-debugging

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

FAQPage Schema
How do I debug memory and handle leaks in Skyline tests?

Debug Skyline test leaks by running a guided investigation workflow that identifies handle, memory, and GC leaks, using dotMemory profiling to capture retention paths and verify fixes.

What is a GC leak and how do I analyze retention paths?

A GC leak occurs when objects are improperly retained and evade garbage collection. Analyze retention paths by using profiling tools like dotMemory to trace the reference graph holding the leaked objects in memory.

How do I triage handle and memory leaks found in nightly CI builds?

Triage leaks in nightly CI builds by analyzing test execution logs to identify symptoms, reproducing the failing tests locally, and capturing retention paths to guide reliable fixes.

Can I use dotMemory to diagnose GC leaks in local debugging sessions?

Yes, dotMemory is used during local debugging sessions to profile test execution, track GC leaks, and identify the specific retention paths keeping objects in memory.

What's the best way to investigate failing Skyline tests showing leak symptoms?

The best way to investigate failing Skyline tests is to execute a step-by-step leak investigation workflow that uses dotMemory profiling to identify retention paths and stabilize the tests.