Object holding count 0 is not freed

Question

Why is my object in the next leak path not freed?

The trace says its reference count is 0, so why is it not freed?
An object is a custom class that comes directly from NSObject . all i do with it is alloc it, init it, copy some lines / numbers from it and send release , but still it is considered a leak and not freed. I see this under the appropriations in the instruments as “living,” so they really don't release him. I create hundreds of these objects, so I can’t let them live.
How can I make this object free? why is he not released first?

Answer 1

Well, it looks like you forgot to call [super dealloc] in your -dealloc method. We all did it. :)

Thus, the object receives a call to dealloc, as expected, but is not actually freed.