12

I would like to make a method that takes in a block, saves it in a member, starts up an asynch task, and then calls the block when the asynchronous call makes its completion callback.

Do I have to retain the block? Are blocks memory managed the same way as any other object? Can I synthesize a property to hold the block?

evilfred
  • 2,314
  • 4
  • 29
  • 44
  • 4
    Excellent explanation of this at [bbum's weblog-o-mat](http://www.friday.com/bbum/2009/08/29/blocks-tips-tricks/). Items five and six in this particular post are relevant to your question, but the whole article is absolutely worth reading. – jscs May 20 '11 at 03:33

2 Answers2

36

Blocks are similar to other objects for memory management, but not the same. When a block which accesses local variables is created, it is created on the stack. This means that it is only valid as long as its scope exists. To save this block for later, you must copy it, which copies it to the heap. Therefore, to protect against problems with such blocks, you should copy, not retain, your block before you store it in an instance variable.

ughoavgfhw
  • 39,734
  • 6
  • 101
  • 123
  • 1
    Although you can retain it after the initial copy. (Although 2: copy is equivalent to retain after the first one.) – jscs May 20 '11 at 03:31
2

You'll have to copy the block, yes. Blocks are regular Objective-C objects.

Dave DeLong
  • 242,470
  • 58
  • 448
  • 498