Help debugging iPhone app - EXC_BAD_ACCESS

Question

I\'ve developed my application using my 3G device to test with. Upon giving this to a friend to test, he\'s noticed that it crashes..I\'ve had a look at the crash log, but i

Answer 1

You may be over-releasing something. If you're running Snow Leopard, run the Static Analyzer (Cmd-Shift-A) and look for memory errors.

The fact that it crashes after a memory error suggests that a UIViewController has released its view. Do you have any UIViewControllers that observe NSNotifications, or otherwise might change their IBOutlets while they are off-screen? This is a common cause of this kind of crash. Make sure you're correctly memory managing your IBOutlets. UIViewControllers should never mess with their IBOutlets (or their UI components at all) when they are off screen. Even if you don't make this mistake, if you're not implementing things as noted in the above link, you can still crash after memory warnings.

MemoryWarning was a pretty good idea, and things have improved, but Apple still hasn't quite cooked all the issues around how it plays with UIViewController. The developer still needs to be very careful.

Answer 2

You should have your friend come to your computer and run it with NSZombieEnabled. That's the best way to debug these issues.