Why is @autoreleasepool still needed with ARC?

by

ARC doesn’t get rid of retains, releases and autoreleases, it just adds in the required ones for you. So there are still calls to retain, there are still calls to release, there are still calls to autorelease and there are still auto release pools.

One of the other changes they made with the new Clang 3.0 compiler and ARC is that they replaced NSAutoReleasePool with the @autoreleasepool compiler directive. NSAutoReleasePool was always a bit of a special “object” anyway and they made it so that the syntax of using one is not confused with an object so that it’s generally a bit more simple.

So basically, you need @autoreleasepool because there are still auto release pools to worry about. You just don’t need to worry about adding in autorelease calls.

An example of using an auto release pool:

- (void)useALoadOfNumbers {
    for (int j = 0; j < 10000; ++j) {
        @autoreleasepool {
            for (int i = 0; i < 10000; ++i) {
                NSNumber *number = [NSNumber numberWithInt:(i+j)];
                NSLog(@"number = %p", number);
            }
        }
    }
}

A hugely contrived example, sure, but if you didn’t have the @autoreleasepool inside the outer for-loop then you’d be releasing 100000000 objects later on rather than 10000 each time round the outer for-loop.

Update:
Also see this answer – https://stackoverflow.com/a/7950636/1068248 – for why @autoreleasepool is nothing to do with ARC.

Update:
I took a look into the internals of what’s going on here and wrote it up on my blog. If you take a look there then you will see exactly what ARC is doing and how the new style @autoreleasepool and how it introduces a scope is used by the compiler to infer information about what retains, releases & autoreleases are required.

More Related Contents:

  1. Some questions about Automatic Reference Counting in iOS5 SDK
  2. Weak NSString variable is not nil after setting the only strong reference to nil
  3. In which situations do we need to write the __autoreleasing ownership qualifier under ARC?
  4. With ARC, what’s better: alloc or autorelease initializers?
  5. When to use -retainCount?
  6. How does the new automatic reference counting mechanism work?
  7. How do I avoid capturing self in blocks when implementing an API?
  8. Why would you use an ivar?
  9. Disable Automatic Reference Counting for Some Files
  10. Handling Pointer-to-Pointer Ownership Issues in ARC
  11. How does the NSAutoreleasePool autorelease pool work?
  12. ARC and bridged cast
  13. AVAudioPlayer not playing any sound
  14. @property definitions with ARC: strong or retain?
  15. NSString to CFStringRef and CFStringRef to NSString in ARC?
  16. Does ARC work with Core Graphics objects?
  17. Why has NSNumber such strange retainCounts?
  18. Tagged pointers in Objective-C
  19. Instance variables declared in ObjC implementation file
  20. Is it possible to debug “Terminated due to memory error”?
  21. Retain Cycle in ARC
  22. When converting a project to use ARC what does “switch case is in protected scope” mean?
  23. Property vs. ivar in times of ARC
  24. How to enable ARC for a single file
  25. AVAudioPlayer stops playing immediately with ARC
  26. Custom dealloc and ARC (Objective-C)
  27. Why does ARC retain method arguments?
  28. NSError and __autoreleasing
  29. How to visually create and use static cells in a UITableView embedded in a UIViewController
  30. What is the difference between a __weak and a __block reference?

Leave a Comment