Memory Management in Objective-C

1. Manual Retain Release (MRR)

MRR (also called Manual Reference Counting) requires developers to explicitly manage object lifetimes. All Objective-C classes inherit from NSObject, which provides reference counting capabilities.

How MRR Works

• Every object has a reference count
• Each retain increases the count by 1
• Each release decreases the count by 1
• When the count reaches 0, the object is deallocated

---

Core MRR Rules (Very Important)

1. Ownership Rule
   You own an object if you create it using:
   • alloc
   • new
   • copy
   • mutableCopy
2. Retain Rule
   If you want to keep an object you didn’t create, you must call retain.
3. Release Rule
   Every retain or ownership must be balanced with a release or autorelease.
4. No Double Release
   Never release an object you don’t own or release an object more than once.

---

Example: Manual Retain Release (MRR)

#import <Foundation/Foundation.h>

@interface ExampleClass : NSObject
- (void)exampleMethod;
@end

@implementation ExampleClass
- (void)exampleMethod {
    NSLog(@"Memory is manually managed!");
}

- (void)dealloc {
    NSLog(@"Memory cleaned up successfully");
    [super dealloc];
}
@end

int main() {
    ExampleClass *exampleObject = [[ExampleClass alloc] init];
    [exampleObject exampleMethod];

    NSLog(@"Reference count after allocation: %lu", [exampleObject retainCount]);
    [exampleObject retain];

    NSLog(@"Reference count after retain: %lu", [exampleObject retainCount]);
    [exampleObject release];

    NSLog(@"Reference count after release: %lu", [exampleObject retainCount]);
    [exampleObject release];

    exampleObject = nil;
    return 0;
}

Output

Memory is manually managed!
Reference count after allocation: 1
Reference count after retain: 2
Reference count after release: 1
Memory cleaned up successfully

---

Problems with MRR

• Easy to introduce memory leaks
• Risk of over-release crashes
• Code becomes verbose and error-prone
• Hard to maintain in large projects

Because of these issues, Apple introduced ARC.

---

ARC was introduced in 2011 to simplify memory management. It automatically inserts retain, release, and autorelease calls at compile time.

ARC is not garbage collection — it is compile-time reference counting.

---

Benefits of ARC

• Eliminates manual retain / release
• Reduces memory leaks
• Cleaner and shorter code
• Better performance through compiler optimizations

---

Key Rules Under ARC

• You cannot use:
  • retain
  • release
  • autorelease
  • retainCount
• Use @autoreleasepool instead of NSAutoreleasePool
• Ownership rules still exist but are enforced automatically

---

Example: Automatic Reference Counting (ARC)

#import <Foundation/Foundation.h>

@interface ExampleClass : NSObject
- (void)exampleMethod;
@end

@implementation ExampleClass
- (void)exampleMethod {
    NSLog(@"Memory is automatically managed!");
}

- (void)dealloc {
    NSLog(@"Memory cleaned up successfully");
}
@end

int main() {
    @autoreleasepool {
        ExampleClass *exampleObject = [[ExampleClass alloc] init];
        [exampleObject exampleMethod];
        exampleObject = nil;
    }
    return 0;
}

Result

Memory is automatically managed!
Memory cleaned up successfully

---

Memory Management in Objective-C

Feature	MRR	ARC
Manual retain/release	Yes	No
Risk of memory leaks	High	Low
Code verbosity	High	Low
Compiler assistance	No	Yes
Recommended today	❌ No	✅ Yes

---

In MRR

NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
// code
[pool drain];

In ARC

@autoreleasepool {
    // code
}

---

• Always use ARC for modern Objective-C projects
• Avoid retainCount even in MRR (it is unreliable)
• Use weak references to avoid retain cycles
• Be careful with blocks and delegates
• Use Instruments (Leaks, Allocations) to detect memory issues

---

Objective-C memory management ensures efficient and safe use of system resources.

• MRR requires manual retain and release calls and is error-prone
• ARC automates reference counting, reducing bugs and simplifying code
• Modern Objective-C development always uses ARC