dpearson2699/swift-ios-skills / skills/ios-memgraph-analysis
ios-memgraph-analysis
VerifiedUse when capturing or analyzing an iOS .memgraph, especially when the task mentions a memory leak, heap growth, persistent memory increase, ownership path, or matched-capture comparison with Apple CLI tools. Covers unambiguous Simulator capture, leaks/heap/vmmap/malloc_history evidence, raw artifact preservation, and same-flow verification. Use debugging-instruments for interactive Xcode Memory Graph, Instruments, generic retain-cycle inspection, or LLDB work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.4 KB |
| evals/evals.json | config | 4.1 KB |
| references/reachable-growth.md | markdown | 1.8 KB |
| scripts/capture_sim_memgraph.pyexecutable | script | 6.7 KB |
| scripts/summarize_memgraph.pyexecutable | script | 13.5 KB |
references/reachable-growth.md
View on GitHub# Reachable Growth When `leaks` Is Empty
Load this workflow only after a matched lifetime produces no unreachable leak
but baseline and post-flow graphs show persistent growth.
## Contents
- [Match the Captures](#match-the-captures)
- [Locate the Growing Region](#locate-the-growing-region)
- [Find a Suspicious Address](#find-a-suspicious-address)
- [Trace Ownership](#trace-ownership)
- [Preserve Evidence](#preserve-evidence)
## Match the Captures
Capture baseline and post-flow graphs from the same app build, process, device
or Simulator, launch state, and user flow. Repeated post-flow growth is stronger
evidence than a single large snapshot.
## Locate the Growing Region
Run `vmmap -summary` on both graphs. If growth is in malloc regions, compare the
graphs with the installed `heap` tool's current syntax:
```bash
heap --diffFrom=baseline.memgraph post.memgraph
```
Treat the result as a type/size lead, not as proof of ownership.
## Find a Suspicious Address
Obtain an address for a growing app-owned type or size:
```bash
heap --addresses='<class-or-size-pattern>' post.memgraph
```
Record the query and selected address so the next step is reproducible.
## Trace Ownership
- Without Malloc Stack Logging, use `leaks --traceTree=<address>` to find the
live ownership path.
- With Malloc Stack Logging, use
`malloc_history post.memgraph -fullStacks <address>` for allocation evidence.
- Use `leaks --referenceTree --groupByType` when aggregate ownership clues are
more useful than a single path.
Stop at the first strong app-owned edge. A framework node, allocation stack, or
type-count delta alone does not identify the lifetime bug.
## Preserve Evidence
Check each installed tool's `--help` because Xcode/macOS output and flags can
evolve. Preserve raw command output beside both graphs, then repeat the same
queries after the ownership fix.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |