The app that I created and am now testing is crashing on my iPod Touch 2nd gen because I don't have sufficient memory to run the app. I'm assuming that it's talking about RAM but just in case I've ensured that I have at least 2GB of space on my iPod. The app is set to be compatible for iOS 4.2+. My iPod is 4.2 (the highest possible for a 2nd gen iPod touch). All of the iPhones that I've tested it on run it perfectly. I have restarted my iPod before running the app to ensure that there is nothing else running in the background that would be taking up memory. From my understanding, iPod 2nd gens have 128Mb of RAM. Is there any reason why my buzztouch app would require more RAM than that? Is there a way around it? Thanks!

Havn't heard this before, Who knows really, funny. I can say that it's not related to memory, iPad 2nd gen is fine. However, could a certain screen type be going crazy and hogging tons of memory and we don't quite realize it? Running this screen on 2nd gen iPad may simply be exposing an issue that's happening on the other devices too but not crashing. hmmm. What screen is crashing? All of them? the home screen? What type of screen is it? Is loading hundreds of photos or tons of map locations, etc, etc, Thinking out loud here. Gonna have to try to figure out what screen this is or if it's the app itself.

iPod Touch 2nd gen, not iPad :) I've got about 8.5Mb of pictures in my BT_images folder, and over 3,000 screens (mostly menus and image galleries) in my project. Safe to say that with such a big app I can expect problems; I'm puzzled simply because they work on iPhones perfectly. When I open the app it has a black screen and the status bar, but after about 15 seconds of that black screen, it crashes. I can't even get to the splash screen or main screen. I'm taking out all of the screen data urls to make the app offline anyways and am hoping that maybe the app is getting caught up in trying to load so many screens in addition to connecting with the screen data urls?

Hmm, maybe a new record. 3000 screens IN the app - yikes. Could be cool but may also be exactly the problem. Try this as a test: a) Copy the giant BT_config.txt file and paste it somewhere on your computer so you have a backup. b) Hack out nearly ALL the items in the screens[] array so you only have a few. c) Test. See if it crashes. Not sure if this matters or not but the idea is to see if that indeed is the issue. All of these screens need 'processed' when the app loads and you may be right - could be excessive? Dunno.