objective-c-arc-patterns

name	Objective-C ARC Patterns
user-invocable	false
description	Use when automatic Reference Counting in Objective-C including strong/weak references, retain cycles, ownership qualifiers, bridging with Core Foundation, and patterns for memory-safe code without manual retain/release.
allowed-tools	[]

Objective-C ARC Patterns

Introduction

Automatic Reference Counting (ARC) is Objective-C's memory management system that automatically inserts retain and release calls at compile time. ARC eliminates most manual memory management while providing deterministic memory behavior and preventing common memory bugs like use-after-free and double-free.

Unlike garbage collection, ARC provides immediate deallocation when reference counts reach zero, making it suitable for resource-constrained environments like iOS. Understanding ARC's ownership rules, qualifiers, and patterns is essential for writing memory-safe Objective-C code and avoiding retain cycles.

This skill covers strong and weak references, ownership qualifiers, retain cycles, Core Foundation bridging, and best practices for ARC-based memory management.

Strong and Weak References

Strong references maintain ownership of objects and prevent deallocation, while weak references observe objects without preventing deallocation.

// Strong references (default)
@interface Person : NSObject
@property (nonatomic, strong) NSString *name;
@property (nonatomic, strong) NSArray *friends;
@property (nonatomic, strong) UIImage *photo;
@end

@implementation Person
@end

// Weak references
@interface ViewController : UIViewController
@property (nonatomic, weak) id<ViewControllerDelegate> delegate;
@property (nonatomic, weak) IBOutlet UILabel *nameLabel;
@end

@implementation ViewController
@end

@protocol ViewControllerDelegate <NSObject>
- (void)viewControllerDidFinish:(ViewController *)controller;
@end

// Using strong and weak
void strongWeakExample(void) {
    Person *person = [[Person alloc] init];
    person.name = @"Alice"; // Strong reference to NSString

    __weak Person *weakPerson = person; // Weak reference
    NSLog(@"Weak person: %@", weakPerson.name);

    person = nil; // Person deallocated
    NSLog(@"After nil: %@", weakPerson); // weakPerson is now nil
}

// Unowned references (unsafe_unretained)
@interface NodeOld : NSObject
@property (nonatomic, unsafe_unretained) NodeOld *parent;
@property (nonatomic, strong) NSArray<NodeOld *> *children;
@end

@implementation NodeOld
@end

// Weak vs unowned
@interface CommentOld : NSObject
@property (nonatomic, strong) NSString *text;
@property (nonatomic, weak) PostOld *post; // Weak: can be nil
@end

@interface PostOld : NSObject
@property (nonatomic, strong) NSArray<CommentOld *> *comments;
@end

@implementation CommentOld
@end

@implementation PostOld
@end

// Strong captures in blocks
void blockCaptureExample(void) {
    Person *person = [[Person alloc] init];
    person.name = @"Bob";

    // Strong capture
    void (^strongBlock)(void) = ^{
        NSLog(@"%@", person.name); // Captures person strongly
    };

    // Weak capture to avoid retain cycle
    __weak Person *weakPerson = person;
    void (^weakBlock)(void) = ^{
        NSLog(@"%@", weakPerson.name); // Captures weakly
    };

    strongBlock();
    weakBlock();
}

Strong references increment retain count, while weak references are automatically set to nil when the object deallocates, preventing dangling pointers.

Retain Cycles and Breaking Them

Retain cycles occur when objects hold strong references to each other, preventing deallocation. Breaking cycles requires weak or unowned references.

// Retain cycle example
@interface Parent : NSObject
@property (nonatomic, strong) NSArray<Child *> *children;
@end

@interface Child : NSObject
@property (nonatomic, weak) Parent *parent; // Weak to break cycle
@property (nonatomic, strong) NSString *name;
@end

@implementation Parent
- (void)dealloc {
    NSLog(@"Parent deallocated");
}
@end

@implementation Child
- (void)dealloc {
    NSLog(@"Child deallocated");
}
@end

void noCycleExample(void) {
    Parent *parent = [[Parent alloc] init];
    Child *child = [[Child alloc] init];
    child.name = @"Alice";
    child.parent = parent; // Weak reference

    parent.children = @[child]; // Strong reference
    // When parent goes out of scope, both deallocate
}

// Delegate pattern without cycles
@protocol DataSourceDelegate <NSObject>
- (void)dataSourceDidUpdate:(id)source;



 (, ) <DataSourceDelegate> delegate;
- ()fetchData;



- ()fetchData {
    
    [.delegate dataSourceDidUpdate:];
}

- ()dealloc {
    ();
}




 (, )  *baseURL;
- ()fetchDataWithCompletion:( (^)( *data))completion;



- ()fetchDataWithCompletion:( (^)( *))completion {
    
    (dispatch_get_global_queue(
        DISPATCH_QUEUE_PRIORITY_DEFAULT, ), ^{
         *data = [ dataUsingEncoding:];
        (dispatch_get_main_queue(), ^{
            completion(data);
        });
    });
}

- ()dealloc {
    ();
}




 (, ) NetworkManager *networkManager;



- ()loadData {
    __ () weakSelf = ;
    [.networkManager fetchDataWithCompletion:^( *data) {
        __ (weakSelf) strongSelf = weakSelf;
         (!strongSelf) ;

        
        (, strongSelf.view);
    }];
}

- ()dealloc {
    ();
}




 (, )  *observers;
- ()addObserver:()observer;
- ()removeObserver:()observer;
- ()notifyObservers;



- ()init {
     = [ init];
     () {
        _observers = [ array];
    }
     ;
}

- ()addObserver:()observer {
    
    [.observers addObject:[ valueWithPointer:(__bridge  *)observer]];
}

- ()removeObserver:()observer {
    [.observers removeObject:[ valueWithPointer:(__bridge  *)observer]];
}

- ()notifyObservers {
     ( *value  .observers) {
         observer = (__bridge )( *)[value pointerValue];
         (observer) {
            
        }
    }
}

Always use weak references for delegates, parent pointers, and observers to break retain cycles. Use the weak-strong dance in blocks for safe self access.

Ownership Qualifiers

ARC provides ownership qualifiers that explicitly control memory management behavior for variables and properties.

// Property ownership qualifiers
@interface Container : NSObject

// Strong: default for object pointers
@property (nonatomic, strong) id strongProperty;

// Weak: doesn't prevent deallocation
@property (nonatomic, weak) id weakProperty;

// Copy: creates a copy of the object
@property (nonatomic, copy) NSString *name;
@property (nonatomic, copy) NSArray *items;

// Assign: for non-object types
@property (nonatomic, assign) NSInteger count;
@property (nonatomic, assign) CGFloat value;

// Unsafe_unretained: weak without nil-ing
@property (nonatomic, unsafe_unretained) id unsafeProperty;

@end

@implementation Container
@end

// Variable qualifiers
void qualifierExamples(void) {
    // __strong: default qualifier
    __strong NSString *strongString = @"Hello";

    // __weak: weak reference
    __  *weakString = strongString;

    
    __  *unsafeString = strongString;

    
     * __autoreleasing error;
}



 (, )  *text;
 (, )  *recipients;





 copyPropertyExample() {
    Message *message = [[Message alloc] init];

     *mutableText = [ stringWithString:];
    message.text = mutableText; 

    [mutableText appendString:];
    (, message.text); 
    (, mutableText); 
}


 loadData( **outData,  **outError) {
     (outData) {
        *outData = [ dataUsingEncoding:];
    }
     ;
}

 autoreleaseExample() {
     *data;
     *error;

     (loadData(&data, &error)) {
        (, data);
    }  {
        (, error);
    }
}





 (, , )  *identifier;


 (, , )  *name;


 (, , ) <> delegate;


 (, , )  *items;

Choose copy for properties that accept mutable types like NSMutableString or NSMutableArray to prevent unexpected mutations.

Core Foundation Bridging

Core Foundation objects require explicit memory management and bridging to work correctly with ARC-managed Objective-C objects.

// Toll-free bridging with __bridge
void bridgingExample(void) {
    NSString *nsString = @"Hello";

    // Bridge to CF without transfer
    CFStringRef cfString = (__bridge CFStringRef)nsString;
    // nsString retains ownership

    // Bridge back to NS
    NSString *nsString2 = (__bridge NSString *)cfString;
}

// Transferring ownership to CF
void bridgeRetainExample(void) {
    NSString *nsString = @"Hello";

    // Transfer ownership to CF
    CFStringRef cfString = (__bridge_retained CFStringRef)nsString;
    // Must manually CFRelease

    // Use cfString
    CFIndex length = CFStringGetLength(cfString);
    NSLog(@"Length: %ld", (long)length);

    // Release manually
    CFRelease(cfString);
}

// Transferring ownership from CF
void bridgeTransferExample(void) {
    // Create CF object (owned)
    CFMutableStringRef cfString = CFStringCreateMutable(NULL, 0);
    CFStringAppend(cfString, CFSTR("Hello"));

    // Transfer to ARC
    NSMutableString *nsString = (__bridge_transfer NSMutableString *)cfString;
    // ARC now owns, no CFRelease needed

    [nsString appendString:];
    (, nsString);
}


 cfCollectionExample() {
    
     cfArray = (
        ,
        (  *[]){, , },
        ,
        &kCFTypeArrayCallBacks
    );

    
     *nsArray = (__bridge_transfer  *)cfArray;
    (, nsArray);
}


 cfPropertyListExample() {
     *dict = @{: };

    
     plist = (__bridge_retained )dict;

    
     url = (__bridge )[ fileURLWithPath:];
    (plist, url, kCFPropertyListXMLFormat_v1_0, , );

    (plist);
}


 myCFArrayApplierFunction(  *value,  *context) {
     *string = (__bridge  *)value;
    (, string);
}

 cfCallbackExample() {
     cfArray = (__bridge )@[, , ];

    (
        cfArray,
        (, (cfArray)),
        myCFArrayApplierFunction,
        
    );
}

Use __bridge for temporary bridging, __bridge_retained when transferring to CF, and __bridge_transfer when transferring from CF to ARC.

ARC and C Structures

When mixing ARC objects with C structures, explicit memory management is required for object pointers in structures.

// Struct with object pointers
typedef struct {
    __unsafe_unretained NSString *name;
    NSInteger age;
} PersonStruct;

void structExample(void) {
    PersonStruct person;
    person.name = @"Alice"; // Must use __unsafe_unretained
    person.age = 30;

    NSLog(@"Person: %@, %ld", person.name, (long)person.age);
}

// Better: Use Objective-C class instead
@interface PersonData : NSObject
@property (nonatomic, strong) NSString *name;
@property (nonatomic, assign) NSInteger age;
@end

@implementation PersonData
@end

// Struct with manual memory management
typedef struct PersonStructManual {
    CFStringRef name; // Use CF types for retained ownership
    NSInteger age;
} PersonStructManual;

PersonStructManual createPerson(NSString *name, NSInteger age) {
    PersonStructManual person;
    person.name = CFBridgingRetain(name); // Retain manually
    person.age = age;
    return person;
}

void releasePerson(PersonStructManual person) {
    CFRelease(person.name); // Release manually
}

 manualStructExample() {
    PersonStructManual person = createPerson(, );
    
    releasePerson(person);
}


  {
    __  *items;
     count;
} ContainerStruct;


  {
     *items; 
     count;
} ContainerStructPointer;

 pointerStructExample() {
     *array = @[@, @, @];

    ContainerStructPointer container;
    container.items = (__bridge  *)array;
    container.count = array.count;

    
     *retrieved = (__bridge  *)container.items;
    (, retrieved);
}

Avoid storing ARC-managed objects in C structures. Use Objective-C classes or CF types with manual management instead.

Autorelease Pools

Autorelease pools manage temporary objects created by convenience methods and prevent memory buildup in loops.

// Implicit autorelease pool in main
int main(int argc, char *argv[]) {
    @autoreleasepool {
        return UIApplicationMain(argc, argv, nil,
            NSStringFromClass([AppDelegate class]));
    }
}

// Explicit autorelease pools in loops
void processLargeDataset(void) {
    NSArray *items = /* large array */;

    for (id item in items) {
        @autoreleasepool {
            // Temporary objects released each iteration
            NSString *processed = [item description];
            NSData *data = [processed dataUsingEncoding:NSUTF8StringEncoding];
            // data and processed released at end of iteration
        }
    }
}

// Without autorelease pool (memory builds up)
void inefficientLoop(void) {
    for (NSInteger i = 0; i < 1000000; i++) {
        NSString *string = [NSString stringWithFormat:@"Number %ld", (long)i];
        // string not released until end of outer pool
    }
}

// With autorelease pool (memory released each iteration)
void efficientLoop(void) {
    for (NSInteger i = 0; i < 1000000; i++) {
        @autoreleasepool {
             *string = [ stringWithFormat:, ()i];
            
        }
    }
}


 nestedPools() {
     {
         *outer = ;

         {
             *inner = [ stringWithFormat:, outer];
            
        }

        
    }
}


 backgroundWork() {
    (dispatch_get_global_queue(
        DISPATCH_QUEUE_PRIORITY_DEFAULT, ), ^{
         {
            
             *result = [ stringWithFormat:];
            (, result);
        }
    });
}

Use explicit autorelease pools in tight loops that create many temporary objects to prevent memory growth between autorelease pool drains.

Best Practices

1. Use weak for delegates and parent references to break retain cycles in common delegation and hierarchical patterns

2. Apply weak-strong dance in blocks when capturing self to prevent cycles while ensuring safe access during execution

3. Choose copy for mutable type properties like NSString and NSArray to prevent unexpected mutations by callers

4. Annotate nullability explicitly with nullable/nonnull to improve API clarity and Swift interoperability

5. Use autorelease pools in loops that create temporary objects to prevent memory buildup in long-running iterations

6. Bridge CF types explicitly with appropriate qualifiers to manage ownership transfer between ARC and manual reference counting

7. Avoid storing objects in C structs as ARC cannot manage them; use Objective-C classes or CF types instead

8. Check for nil after weak references as they can become nil at any time when the referenced object deallocates

9. Use NSPointerArray for weak collections when maintaining collections of observers or delegates to prevent cycles

10. Profile with Instruments to detect retain cycles, memory leaks, and excessive autoreleased object creation

Common Pitfalls

1. Creating retain cycles with strong delegates causes memory leaks; always use weak for delegate properties

2. Capturing self strongly in blocks without weak creates cycles when blocks are stored in properties

3. Forgetting strong reference in weak-strong dance allows self to deallocate during block execution

4. Using strong for parent pointers creates bidirectional strong references and prevents deallocation

5. Not using copy for NSString properties allows callers to pass mutable strings and modify them later

6. Bridging CF types incorrectly causes over-releases or leaks depending on ownership transfer direction

7. Storing ARC objects in C structures leads to premature deallocation or crashes as ARC cannot track them

8. Creating NSTimer without invalidation retains target strongly and prevents deallocation until invalidated

9. Missing autorelease pools in tight loops causes memory growth and potential crashes from memory pressure

10. Using unsafe_unretained instead of weak creates dangling pointers that crash when accessed after deallocation

When to Use This Skill

Use ARC patterns when writing Objective-C code for iOS, macOS, watchOS, or tvOS to ensure memory-safe applications without manual retain/release calls.

Apply weak references and the weak-strong dance when implementing delegates, observers, or callbacks that could create retain cycles.

Employ proper bridging when interfacing with Core Foundation, Core Graphics, or other C-based frameworks that use manual reference counting.

Leverage autorelease pools when processing large datasets, importing data, or performing other operations that create many temporary objects in loops.

Use appropriate ownership qualifiers when designing public APIs to clearly communicate memory management expectations to clients.

Resources

• Transitioning to ARC Release Notes
• Advanced Memory Management Programming Guide
• Working with Objective-C
• Instruments User Guide
• Core Foundation Design Concepts