IPhone Objective C Memory Allocation

Question

I understand that when using Alloc, new or copy you own the object and need to release the object. I understand that if I retain an object that I need to release it.

But if I have the following statment at the end of a method:

return [[UIImage alloc] initWithContentsOfFile:path];

I own the UIImage object becaused I allocated the memory space, but I dont have a reference to it anymore because it was returned to the caller. In my dealloc() method I can't release it, since I dont have a reference.

So my question is, is this correct:

return [[[UIImage alloc] initWithContentsOfFile:path] autorelease];

I beleive in this case the caller then can retain the returned object if they like to take ownership and will eventually need to release themselves.

Thanks for your help.

score 5 · Answer 1 · answered Aug 20 '12 at 14:13

5

Your assumptions are right. When you're returning an object, you should pass it as an autorelease object.

You use autorelease when you need to send a deferred release message—typically when returning an object from a method...

answered Aug 20 '12 at 14:13

Alexander

8,117
1
35
46

1

Thanks, but when using ARC I guess then I wouldnt use autorelease and let the compiler do all the memory management. – NYTom Aug 20 '12 at 14:18
Yes, ARC will take care to send release to all objects. – Alexander Aug 20 '12 at 14:20

score 4 · Accepted Answer · answered Aug 20 '12 at 14:19

The whole point of autorelease was built around returning objects.

- (id)bad {
    MyObj *obj = [[MyObj alloc] init];
    return obj;
}

This code returns everything correctly, but you (as developer) must be sure to release the object later on.

- (id)moreBad {
    MyObj *obj = [[MyObj alloc] init];
    return [obj release];
}

This code uses the memory as expected, balancing retain and release in one scope, but returned object is garbage now (expect this to crash).

- (id)good {
    MyObj *obj = [[MyObj alloc] init];
    return [obj autorelease];
}

This code is "delayed release". I.e. you can retain the object at the caller side and the object would be safe. It could surely be broken if you don't have NSAutoreleasePool in scope, but that's a pretty rare condition, and you mostly know when that happens (the most common scenario is to start a new thread where there is no "default" autorelease pool).

So, the common practice is to balance the retain (and retain-like) and release methods in one scope. Next suggestion is to always have objects alloc-init-autoreleased, and switch to distinct releases if you have memory issues (like autoreleasing lots of objects in a loop). Next suggestion is to switch to ARC.

Props for the thorough explanation. – Alexander Aug 20 '12 at 14:24 — Alexander, Aug 20 '12 at 14:24

John Smith · Answer 3 · 2012-08-20T14:41:19.560

0

Why trying to alloc it? Just say:

return [UIImage imageWithContentsOfFile:path];

Nothing to alloc - nothing to release.

Also, this is the best option while using ARC, where a releasing attempt leads to error.

edited Aug 20 '12 at 14:41

answered Aug 20 '12 at 14:13

John Smith

2,012
1
21
33

2

I agree, the UIImage class has a method like that so I dont need to alloc, the UIImage class would own the object since its allocating memory itself. I was just using UIImage as an example of returning an instance of a class that you allocated. – NYTom Aug 20 '12 at 14:17
This method actually returns an autoreleased object. – Alexander Aug 20 '12 at 14:21
Well if return a previously allocated object (within the current method, of course), saying "return [object_bla_bla autorelease];" it's enough to avoid memory leaks. Same about "return [[[Bla_bla_Type alloc] initWith_bla_bla_or_whatever] autorelease];" – John Smith Aug 20 '12 at 14:39

score 0 · Answer 4 · answered Aug 20 '12 at 14:19

Both answers are correct, you may however not always have a convenience method at your disposal, so what I like to do is what you've done with autorelease:

- (MySomethingClass*)giveMeAFancyObject{
    MySomethingClass *obj = [[[MySomethingClass alloc] init] autorelease];
    obj.name = @"Something";
    // do some setting up maybe
    return obj;
}

score 0 · Answer 5 · answered Aug 20 '12 at 14:34

If you use release, however, the string will be deallocated before it is returned (and the method would return an invalid object). Using autorelease, you signify that you want to relinquish ownership, but you allow the caller of the method to use the returned string before it is deallocated.

IPhone Objective C Memory Allocation

5 Answers5