I have been developing an application for iPad that is very graphically intensive. I have been able to squeeze quite a bit of performance out already on the iPad 2, but the
The below is my experience. I am quite happy to be corrected...
How are you loading your images?
If you are using:
[UIImage imageNamed:(NSString *)]
Then you need to make sure that there is a good reason to. If you are making heavy use of an image that needs to be cached, then its a good option. Otherwise I would suggest you use
[UIIMage imageWithContentsOfFile:(NSString *)]
iOS appears to have some issues releasing images loaded via imageNamed, even if there are no longer any references to it. Since your app will no longer have any references to the image, you probably wont get the memory warnings. But that doesn't mean that the memory has been freed. iOS tends to keep these images in memory much longer than you would like. When it would normally give a memory warning, it will just terminate the app.
I would also highly recommend turning on Automatic Reference Counting (ARC).
Edit -> Refactor -> Convert to Objective-C ARC...
I had similar issues for quite a while. Making the above changes to my app stopped the crashes, and stopped the memory leak caused when I reloaded the same image over and over again via imageNamed.
Hope that helps.