Opening and closing a certain screen repeatedly makes the app's memory keep growing. In what order would you use Leaks, Allocations, and the Memory Graph?
Start with Allocations, marking a generation every time you open and close the screen to find which objects survive each generation, then pick that object in the Memory Graph to see the reference path of who's holding it, and run Leaks last as a supplement, since it only catches unreachable memory.
Performance and debuggingShort answerBasics
All you've got is vague feedback that "the app is slow." How do you approach that with…
#instruments #allocations
Performance and debuggingShort answerAdvanced
Besides retain cycle leaks, what other kinds of memory bugs do you run into on iOS? And…
#leaks #memory-graph
Memory and ARCShort answerBasics
Think of a memory leak you actually ran into. How did you find it, how did you pin down…
#instruments #memory-graph
Performance and debuggingMultiple choiceIntro
Tapping a certain button freezes the screen for about a second. To see which function on…
#instruments