iOS Memory Graph and Retain Cycle Diagnostic Report

Role: Staff iOS Systems and Performance Optimization Engineer

Context

• Target Bundle: {{target_app_bundle}}
• Profiling Environment: {{profiling_environment}}
• Instruments Leak & Allocation Findings: {{instruments_leak_trace}}
• Suspect View Controllers and Services: {{suspect_view_hierarchy}}
• Memory Footprint Ceiling: {{memory_ceiling_mb}}
• User Interaction Trigger Flow: {{leak_trigger_flow}}

Task

Generate a detailed memory diagnostic report analyzing heap growth and object graph retain cycles in {{target_app_bundle}}, providing exact code-level decoupling techniques to stay under {{memory_ceiling_mb}}.

Method

1. Decode the memory graph signatures provided in {{instruments_leak_trace}} to map unreleased object nodes.
2. Trace parent-child reference topologies between the items in {{suspect_view_hierarchy}}.
3. Isolate escaping closure capture lists, delegate properties missing weak qualifiers, and notification observer lifecycles.
4. Correlate memory accumulation with navigation iterations defined in {{leak_trigger_flow}}.
5. Compare heap allocations before and after the trigger flow against {{memory_ceiling_mb}}.
6. Formulate precise memory decoupling fixes (e.g., weak self, unbinding Combine subscriptions, teardown hooks).
7. Define an automated UI test protocol using XCTest memory metrics to guard against future regressions.

Constraints

• MUST identify the exact strong reference cycle retaining instances of {{suspect_view_hierarchy}}.
• MUST NOT recommend force-unwrapping deallocated references or unsafe unretained pointers (unowned).
• The proposed solution MUST respect memory boundaries within {{memory_ceiling_mb}} on low-memory devices.
• Memory measurements MUST distinguish between dirty memory, clean memory, and compressed memory.

Output format

Provide a technical diagnostic report organized as:

1. Memory Heap & Allocation Overview
2. Retain Cycle Graph Analysis (Visualized ASCII Reference Chain)
3. Closure & Delegate Capture Root Causes
4. Remediation Code Modifications
5. Continuous Profiling & XCTest Validation Script

Self-review

• Verify that the reference graph pinpointed in {{instruments_leak_trace}} is completely resolved.
• Confirm the proposed lifecycle cleanups execute reliably during normal view dismissal.
• Ensure all memory units and thresholds adhere to the specified {{memory_ceiling_mb}} limit.