Memory Leak Causes Crash?

[scoholl]

I'm a bit of a newbie to Objective-C, but I've managed to create a pretty cool game for my iPhone. It's working fine on the Mac, and when I move it to the device it works fine there... for awhile... but then it crashes after about ten minutes of play. I'm able to consistently reproduce the crash. I figure it's some kind of memory leak that's growing to the point where the device can't handle the app anymore (where as the Mac wouldn't be affected so quickly), but for the life of me I can't figure out where this leak may be happening. I've used the Instruments tool to run the app and I can literally see the leak as it happens over and over again, but after that I look at the Instruments tool and say, "Okay, now what?" Again, I'm a newbie (with 10 years of VB), so please don't crucify me for not knowing this, but can someone tell me how in the hell I'm supposed to read the information I receive from the Instruments app? It's a bunch of colored squares and points in memory, but nothing that states, "Okay, this was allocated here, but never released, so..."

Thanks for the help! Just a point in the right direction should be enough.

[RickMaddy]

Actually Instruments is showing you exactly what was allocated and where. Find the colored square representing your application (not code from the SDK). Double click on the last one that is in your own code. This should bring up the file and line in Xcode.

[jsonli]

Originally Posted by RickMaddy

Actually Instruments is showing you exactly what was allocated and where. Find the colored square representing your application (not code from the SDK). Double click on the last one that is in your own code. This should bring up the file and line in Xcode.

Good to know.

[BostonMerlin]

On the detail pane (right side in instruments) look for your file names in those colored boxes.. your leak may not be the last in the list but follow the chain from the bottom up until you find your culprit.

I'm a windows dev for the past twenty years or so.. instruments is different but provides everything you need to know.. you just have to know where to look.

Good luck..
John

[bytor99999]

Is everything in the list that has self % as the left column a line where there is a memory leak? I mean if that is the case, then it thinks lines like

NSArray *nib = [[NSBundle mainBundle] loadNibNamed:@"CalculatorTableCellView" owner:self options:nil];

Are memory leaks. But code like that is taken from books that all have the same code for using a special nib created for a custom Table Cell View.

Thanks

Mark

[svenito]

I'm getting leak reports on the same call. Trying to load a xib for a custom UITableViewCell and leak check reports a memory leak on the

[[NSBundle mainBundle] loadNibNamed: ....

line.

There's no leaks until the table is scrolled.

Can't figure out why though.

[svenito]

Originally Posted by svenito

I'm getting leak reports on the same call. Trying to load a xib for a custom UITableViewCell and leak check reports a memory leak on the

[[NSBundle mainBundle] loadNibNamed: ....

line.

There's no leaks until the table is scrolled.

Can't figure out why though.

I figured it out. Stupidly I forgot to set the identifier of my UITableViewCell in the XIB. I set that and ensured that the identifier passed to the dequeue call matches and I am now leak free.