Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS Memory leak

S

spilakalb

macrumors member
Original poster
Sep 23, 2012
40
0
Code: 
str = [[NSString alloc]initWithString:@"test leak"];
str = [[NSString alloc]initWithString:@"second string"];

In above code there is a leak right? But Instruments Leak not identifying it.

But
Code: 
str = [[NSMutableString alloc]initWithString:@"test leak"];
str = [[NSMutableString alloc]initWithString:@"second string"];
Here leak is identifyiing..Please explain..
 
Last edited by a moderator:
Don't use NSString stringWithString or initWithString.

Your code becomes:

Code: 
str = @"test leak";
str = @"second string";
Do you understand why this will never leak, even though it is against the rules?

I assume you understand why the second example does leak.
 
str = @"test leak";
str = @"second string";
Here @"test leak" doesn't have any refference .So it cause leak right?
 
Is it mandatory to set value is nil after release, to avoid the memory leak?
 
String literals are constants. They cannot leak. They are real NSString objects but they are special and cannot leak. retain, release, autorelease for string constants have no effect.

That is why I said in #2 that that code will never leak.

Also, due to library optimizations stringWithString and initWithString using string literals will return the string literals, not new strings.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back