Both the Leaks instrument and Memory Graph are clean, yet every time you go back and forth to a certain screen, memory on a real device grows by 30MB. What could be the cause in a case like this?
Candidates are reachable abandoned memory (a global cache, a singleton's array, an observer list), objects that are small but hold a large backing store like a decoded bitmap, and resources outside ARC that you have to free yourself, like malloc, CGContext, and Metal textures.
Memory and ARCShort answerBasics
Are "reference cycle" and "memory leak" the same thing?
#leak #abandoned-memory
Memory and ARCShort answerBasics
Think of a memory leak you actually ran into. How did you find it, how did you pin down…
#leak #instruments
Memory and ARCShort answerBasics
A view controller doesn't seem to leave memory after you close its screen. How would you…
#leak
Memory and ARCShort answerIntro
What is a memory leak?
#leak