I need a little help fixing a memory leak

[carsonp]

I am working on an app and am having a problem with a memory leak (according to instruments) and I could use a hand as I am not too great with knowing exactly when to release something.

I've narrowed down the source of the leak to one class and who ever feels up for the challenge of helping me I will PM them the file and the screenshot of the leak from instruments.

I would greatly appreciate the help from someone. I'm still a noob at this when it comes to memory management. Reply if you are up for the task.

[Domele]

Just post the class here or at Pastebin.com - #1 paste tool since 2002!.

[carsonp]

Originally Posted by Domele

Just post the class here or at Pastebin.com - #1 paste tool since 2002!.

here's the .h [Objective C] // // placesViewController.h // That One Place // // Created by Carson Pe - Pastebin.com
the .m [Objective C] // // placesViewController.m // That One Place // // Created by Carson Pe - Pastebin.com

and the screenshot of the leak http://f.cl.ly/items/0g0v1E3W1Y431v2...35.05%20PM.png


thanks

[Domele]

If you double click those leaks, it should show you which line is leaking.

[carsonp]

Originally Posted by Domele

If you double click those leaks, it should show you which line is leaking.

It's very vague and I'm not sure what needs to be done to fix it. That's why I'm asking for help.

[Domele]

Well which line does it point to? That'd probably help a lot.

[carsonp]

Originally Posted by Domele

Well which line does it point to? That'd probably help a lot.

Almost all seem to point to

[self presentModalViewController:addView animated:YES];

on 179

[Duncan C]

Originally Posted by Domele

If you double click those leaks, it should show you which line is leaking.

Actually, the instruments tool usually points to the line that originally creates the leaked object, not the offending code.

I suggest running static analysis on your code. In XCode 4, it's in the product menu, and is simply called "analyze." I don't remember where the analyze command was in XCode 3, since XCode 4 is totally, utterly different in every possible way from XCode 3, for no apparent reason.

[carsonp]

Originally Posted by Duncan C

Actually, the instruments tool usually points to the line that originally creates the leaked object, not the offending code.

I suggest running static analysis on your code. In XCode 4, it's in the product menu, and is simply called "analyze." I don't remember where the analyze command was in XCode 3, since XCode 4 is totally, utterly different in every possible way from XCode 3, for no apparent reason.

I ran the Clang analyzer and fixed all the errors it pointed out. This error is the one left after the analyzer says is all clear.