Memory problem & Leaking ?!?!?

[aryaxt]

I know I asked this question before, but i am still very confused.
My app works perfect on the simulator, but on the iphone it crashes after a while (it's a multi-player game which keeps receiving data and doing stuff)
So i ran the Leaks performance tool, As the application goes I get more leaks.

I still don't understand what is a leak? When should i release objects and how?
What I'm currently doing is calling release on objects only when I created an instance of them through alloc

I have so many classes that inherit from NSObject, and i use alloc to create an instance of them. From what i know release calls the dealloc method in the object. So is it necessary to create a dealloc method for each class that i wrote? Do i need to dealloc the super class?
I tried something like this: [super dealloc]; on the class that I wrote which is being called when i'm done with the object, and that causes the whole application to crash even on the simulator.

I know so many questions I would appreciate any help or tips on this.

[MattjDrake]

You may want to go back and make sure that your class is releasing objects in the dealloc method like so.



Here is a link to a complete article I wrote about using custom classes including a good way to handle memory:

Here is How you Use a Class in Objective-C | How to Make iPhone Apps

One more thing that helps is to use the "retainCount" function. Each object should have this so you can use this to test if your objects seem to be getting over or under released.

Here is how you can write the retain count to the log:

NSLog([NSString stringWithFormat:@"Retain Count:%i", [someObject retainCount]]);

Look up using "NSZombie" as well - I found that to be very helpful in dealing with memory problems.

One more thing: coming up with and following strict rules regarding memory management is a good idea. Good luck, this is a tough issue on the iPhone..

[aryaxt]

Thanks a lot, this is a great help
and explains very well