Reputation: 6763
I have a complex App that runs reliably, but I'm puzzled why I need to retain a particular NSArray ('sources') twice to prevent a crash (although no exception is reported on the console, but the application crashes and returns to the springboard).
A snippet of the code is included below. There's too much code to paste it all, but you have my word that there are no explicit calls to release the array. 'sources' is an instance variable.
If I only retain the array once (or not at all), I get the crash. With two retains, the App is perfectly stable.
NSString *plistPath = [[NSBundle mainBundle] pathForResource:@"Sources" ofType:@"plist"];
sources = [[NSArray arrayWithContentsOfFile:plistPath] autorelease];
[sources retain];
[sources retain];
Thoughts on why I would need to retain this array twice appreciated. Thanks in advance.
Upvotes: 1
Views: 261
Reputation: 11
NSString *plistPath = [[NSBundle mainBundle] pathForResource:@"Sources" ofType:@"plist"];
sources = [[NSArray alloc] initWithContentsOfFile:plistPath];
Upvotes: 1
Reputation: 2918
That's because arrayWithContentsOfFile: returns an autoreleased array to you. Calling autorelease on this array will release it twice at the end of current event run loop.
Upvotes: 2
Reputation: 237060
There is an explicit call to release the array. autorelease
is just as explicit as release
— it just happens later. Not only that, but it was wrong to autorelease the array in the first place, since you didn't own it. One retain
is necessary to claim ownership of the array. The second one prevents the crash by balancing out the incorrect use of autorelease
.
Upvotes: 6
Reputation: 21883
Ditch the autorelease on the factory method. It's why you need a second retain.
Upvotes: 3
Reputation: 19071
You’re using +arrayWithContentsOfFile:
, which returns an autoreleased object, then autoreleasing it again. Take out the call to -autorelease
and you’ll be OK. You could re-write it as so:
sources = [[NSArray arrayWithContentsOfFile:plistPath] retain];
Upvotes: 10
Reputation:
Is it something to do with that autorelease? I can't see why that's there: it should be the factory method that autoreleases. Although I don't know what the consequence of adding an extra autorelease is, it might be worth seeing what happens if you take that out along with one of the retains.
Upvotes: 3