iOS Memory Leak and Retain Cycle Remediation Plan

Role: Principal iOS Performance and Debugging Engineer specializing in Memory Graph Analysis and Xcode Instruments diagnostics.

Context

• Target iOS module: {{app_module_name}}
• Metric or crash signal: {{crash_rate_metric}}
• Target screens or user flows: {{affected_screens}}
• Diagnostic traces and tool findings: {{instruments_findings}}
• Target hardware profile: {{reproduction_device_matrix}}

Task

Formulate a rigorous debugging, remediation, and architectural containment plan to eliminate retain cycles, unbounded memory growth, and Jetsam OOM crashes in {{app_module_name}} across {{affected_screens}} based on {{instruments_findings}}.

Method

1. Evaluate the provided {{instruments_findings}} to isolate strong reference cycles, lingering closures, and delegate retain patterns.
2. Map the object lifecycle graph from initial view controller presentation to dismissal within {{affected_screens}}.
3. Identify external observer subscriptions (Combine AnyCancellable bags, NotificationCenter, KVO) failing to unregister.
4. Design deterministic memory leak isolation unit tests utilizing weak references and expectation fulfillments.
5. Formulate refactoring guidelines replacing implicit self captures with structured capture lists ([weak self]).
6. Establish image/asset cache limits and background purge routines tailored to {{reproduction_device_matrix}}.
7. Detail a continuous regression prevention pipeline incorporating MemGraph CI assertions to stabilize {{crash_rate_metric}}.

Constraints

• MUST provide actionable code-level fixes rather than generic deallocation advice.
• MUST NOT permit unconstrained memory footprints under background execution transitions.
• All proposed fixes MUST be verifiable via Xcode Memory Graph Debugger or Instruments Leaks template.
• Avoid introducing force unwrap patterns when unwrapping weak self captures.

Output format

Provide the remediation plan in the following structure:

1. Root Cause & Retain Graph Breakdown (max 200 words)
2. Step-by-Step Code Remediation Strategy (ordered by priority)
3. Automated Regression Verification Plan (unit test & CI memory assertions)
4. Target Metric Milestones (measurable recovery targets for {{crash_rate_metric}})

Self-review

• Verify that the plan directly resolves observations in {{instruments_findings}}.
• Confirm that hardware limits for {{reproduction_device_matrix}} are considered in cache sizing.
• Check that weak reference capture rules are explicitly detailed without dangerous force-unwraps.