Xcode - Understanding the Allocations Tool

When profiling an application, I notice that live bytes increase by about 250 KB every time I perform certain actions (including UIViews).

In the list of objects, the main (growing) criminal simply reads as "malloc 144 bytes".

Sometimes I used the Allocations tool to find objects that I have held on longer than I would like, but I'm not sure how to interpret the malloc objects.

Everyone is welcome any guide.

+5
source share
1 answer

A few thoughts:

  • The Allocations tool is great, but first I will focus on the leak . Do you have a clean account there?

  • ( "" "" ). , ARC, .

  • ARC? , .

  • ? , . .

  • , (aka keep cycle)? NSLog dealloc , , ( , ). ( dealloc, NSLog). invalidate NSTimer - , . , , dealloc.

  • / , / ? ( NSLog/breakpoint dealloc , , .)

  • 256 (!) imageNamed image? imageNamed , ( , ).

, , , . .

, , . 144 malloc , 250 . malloc , , , , malloc.

+11

All Articles