Think of a memory leak you actually ran into. How did you find it, how did you pin down the cause, and how did you prove it was fixed?
Reproduce (memory climbing in steps as you re-enter a screen) → pin down (the reference path of an instance that shouldn't be alive in Memory Graph Debugger, Instruments Allocations Generations) → fix → prove (deinit log or breakpoint, and compare the Persistent count after repeating the same scenario before and after).
Memory and ARCShort answerBasics
A view controller doesn't seem to leave memory after you close its screen. How would you…
#leak #memory-graph #deinit
Memory and ARCShort answerExpert
Both the Leaks instrument and Memory Graph are clean, yet every time you go back and…
#leak #instruments
Performance and debuggingShort answerBasics
Opening and closing a certain screen repeatedly makes the app's memory keep growing. In…
#memory-graph #instruments
Memory and ARCShort answerBasics
Are "reference cycle" and "memory leak" the same thing?
#leak