Game Development Community

Startup Crash

by Phillip O'Shea · in iTorque 2D · 03/19/2010 (7:45 pm) · 5 replies

I've got this very irregular issue when loading my app. About 1-2 seconds after launching the app, it just crashes out without any debug information. I suspect that there is a subtle memory issue going on, but I'm not doing anything out of the ordinary.

Anyone here had similar issues?

About the author

Head of Violent Tulip, a small independent software development company working in Wollongong, Australia. Go to http://www.violent-tulip.com/ to see our latest offerings.


#1
03/20/2010 (4:54 am)
Just had this issue yesterday, it turns out that I just upgraded my ipod to os 3.1.3 but my Xcode & iPhone SDK was still based on os 3.0. Upgrading Xcode & iPhone SDK fixed my issue.
#2
03/22/2010 (4:10 pm)
This is getting even more bazaar. The game launches fine for the first X times I play it. After a while, it just suddenly stops launching and will not load at all.

The strange thing is that I don't do anything different on each startup. I don't load any preferences, don't load user data - nothing. I just don't see why on earth it is doing this.

Help!
#3
03/22/2010 (4:46 pm)
because the device runs out of memory which is a common thing on the iphone. Each start of an application eats a bit of memory until the next restart (or force cleans through free memory)

Safari, Mail and iPod player make this worse as they are kept in memory permanentely after they were first started unless they are kicked out forcefully by Free Memory
#4
03/22/2010 (4:58 pm)
I figured it had something to do with memory. Any idea on what I can do?

I literally only load 9 cs files. No user data, no game data. All I load is the bare minimum to get my game to work. I got rid of the config xml loading (just replaced with setting the variables by hand), got rid of all the keybind stuff, everything except Audio and Canvas initialization.

The game appears to shutdown cleanly. I don't get any out-of-the-ordinary console errors. I'm not using any custom memory handling (malloc, etc).

I just haven't got a clue on how to fix this.
#5
03/22/2010 (5:37 pm)
How much memory is Instruments saying that you are using?