Home/ Questions/Q 542433
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T10:26:46+00:00

I’ve developed my application using my 3G device to test with. Upon giving this

  • 0

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 it’s not much use except for the “EXC_BAD_ACCESS” statement after a few memory warnings.

On my device, I can use the imagePicker lots, and each time a photo is taken I get a memory warning, but this doesn’t cause any problems.

On my friend’s device (also a 3G), after a couple of images chosen from the camera, the app crashes.

So, my question is.. I think something is being deallocated because of the memory warning – but only on my friend’s device, and then after deallocation, it’s trying to be used again. How can I find out what object is being called? I can’t use NSZombies because this is a remote (beta) device.

Help please!

Also if anyone has any ideas why my device can pick image after image without any problem and his can’t…that would be most helpful

Thanks!

EDIT: New discovery.. I’m getting this error message too: KERN_PROTECTION_FAILURE which I understand to be something to do with data access. The crash seems to happen right after I save the image got from the UIImagePicker. Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    • 0