Memory management question.

[DrBeak1]

Let me preface this with the fact that I still consider myself a noob to the programing world.

I ran my app in the simulator with the leaks instrument. I found that when I loaded/viewed a certain UIViewController that a number of leaks arose. I've been very mindful (or at least thought I was) of memory management but went back over my code for this view and quadruple checked that in every instance of an alloc, init, etc that I released the object. I can't find any reason why I'm leaking.

As a noob, I'm also new to the leaks instrument but I found what appears to be the leak instrument indicating that the leaks were coming from NSDateComponants (responsible frame: UIDatePickerView) and Malloc (responsible frame:UIKeyboardInputManagerClassForInputMode). Following the assumption that the leaks instrument is pointing to these objects as the leaky culprits I again looked at my code pertaining to these objects, but everything looks fine.

QUESTION: Aside from the "fundamental rule" of memory management are there other places where issues commonly arise that would be worth checking? And am I correct in assuming that the leak instrument is pointing me towards those objects because they are at fault?

[Chilibird]

Leaks, unfortunately, isn't perfect and may present false positives. My understanding is that this is especially true if you do any threading in your code. Due to the nature of how threads and their memory are handled, Leaks may think that an object was leaked when in fact it was properly taken care of (I know I ran into this in my newest app)

In other words, Leaks is great to catch some stuff, but there's no replacement for the human touch