Forum

Just wondering if anyone has any tips on getting rid of memory leaks. I've run the 'fruit' example through Instruments and it seems to have a few, my application extends from this tutorial and seems to have similar leaks (and I'm guessing it's what's causing my crashes). 

Here's the screenshot:

I have no idea why the NSIndexPath would cause a leak, or how to fix it. Any help would be appreciated

Nick.

I think I have solved it!

After reading the post left by daniel, I decided to investigate my choice for releasing the f object.

After some inspection, I realized that the “f” object wasn’t a new instance of Fruit, but a reference to an existing Fruit object.

Releasing this object, removes the Fruit at that cell from memory and causes the app to crash.

So to fix the crashing problem, remove the

[f release];

line from cellForRowAtIndexPath method inside of RootViewController.m.

Thank you to daniel for bringing this to my attention. I will update the tutorial later today.

I've been working with the UITextView and I've come to the conclusion that it's design is faulty. 

You can safely do

[textView setText:@"Blah Blah"];

with no memory leaks what so ever, but when you do

NSString *blah = @”Blah Blah”;

[textView setText:blah];

This creates a memory leak.  They are both the same methods unless i'm not understanding something correctly?  I even tried releasing, autoreleasing, both blah and textView's text, but the methods that run in the background specifically because this is attached to a DOMHTMLElement it has something to do with that.  I first came upon this when I was logging some information and using setText on the textView.  I racked up an easy 1gb of memory =(