Figuring out instrument leaks! so many!!!

[raheel]

This morning is scary. I Started instruments for the first time to toast the completion of my project... only to find soooo mannny leaks! its incredible!

And after watching those things fill up the table. I am now clueless as to what they mean!. Could anyone please explain!

The leaks are coming in when I'm scrolling the tableview. with about 200 cells.
And when I call the InitialiseDatabase method in appdelegate, Many many many more leaks of NSCFString.

And, i'm sure your familiar with SQLiteBooks app from Apple. They have a method called InitialiseDatabase. That is called in ApplicationDidFinishLaunching.

My app calls this method InitialiseDatabase first on touching a UIButton. Then After certain selections in PickerView, my app recals this method again with different sql query string.
This is where i get many many more leaks. On "ReCalling" initialiseDatabase;
My goal was to kinda sort listing and display data on the very same tableview. and reload it! and initialise database empties the array and reloads it with new objects.

Any clues/suggetions/directions would be great!

[smasher]

The first time you check it can be a mess - especially because if you leak an array full of strings, you'll see the array and the 99 strings in the list. So start by looking for arrays and your custom classes in the list - if you clean those up, some of the numbers and strings will disappear from the list.

Click the "details" button at the bottom of the leaks window - that will open up a pane on the right that shows the stack track for that object. That trace will tell you where the object was created, which should help you figure out why it was leaked. You can double-click a frame in that trace to see the exact line where the object was created.

Remember that a "leak" means that you created an object and it was never released properly. The leaks tool knows that it's a leak when you no longer have any pointers to the object; there's no possible way you could release it then. So for each object created in your suspect method, ask yourself "when does this get released?"

[TunaNugget]

Here's a good tutorial. You'll also sometimes get a memory leak from the frameworks. I keep getting one in AVAudioPlayer.