CODEWITHSUNDEEP
iphoneobjective-c
Rocker
Rocker

Reputation: 1487

Game crashes on the actual iPhone but simulator? memory problem?

I have built my first game using Cocos2D. It worked fine on the simulator. But when it runs on the actual iPhone, it crashes. I don know why. Thought it was memory leaks, so i tried to detect, but no leaks found. I tried to increase and decrease frame rate, neither both succeeded. Anyone experienced please help me out. I am really stressed now. If anyone had the same issue please share with me your opinion.

Yours thanksfully.

Upvotes: 2

Views: 276

Answers (5)

Eric Farraro
Eric Farraro

Reputation: 865

I've run into similar issues (I also use Cocos, but I don't think this is Cocos specific). The best thing to do is plug-in your iPhone and watch the stacktrace when it crashes (or retrieve the stacktrace after the fact)

This happened to me a lot because the resources between the iPhone and the simulator were not in sync; in other words, some how resources would be available to the simulator (eg: images) but those same resources were not transferred to the iPhone for whatever reason. Sometimes, if I ran 'clean' on the simulator, I would observe the same issue.

It's extremely frustrating to debug these types of issues, but you'll get used to it.

Upvotes: 1

Frank Schmitt
Frank Schmitt

Reputation: 25775

Without more information, I would try the following steps:

Delete the app from the device and simulator (using the tap-and-hold technique to make your icons jiggle) and reinstall it. Sometimes a setting (or lack of a setting) in the user defaults will cause a crash, and those don't get wiped out unless you delete and re-run your app.

Also try the "simulate memory warning" option in the simulator and see if that gets it to crash.

Upvotes: 0

fbrereto
fbrereto

Reputation: 35935

I have found tools like Instruments and NSZombieEnabled to be very helpful in tracking down issues such as these.

Upvotes: 0

deanWombourne
deanWombourne

Reputation: 38475

I agree with Dominic - we definitely need more information to be able to help you - do you have the output from the console or the stack from the debugger?

Also, while memory leaks are a Bad Thing, they rarely lead to crashes directly. They will increase the amount of memory used by your app so if you're memory intensive then you might get a problem but they're not the first place I'd look to try to debug this.

Try running the app in Instruments and watch the memory usage graph - then not only can you see the total that your app is using but you can get an idea of which sections of your app use the most and can focus your efforts in reducing it.

Sam

Upvotes: 0

Mo.
Mo.

Reputation: 15363

Sorry, but you need to specify more details. How does it crash? What does the error log say? One thing you might look into is the amount of memory, your game consumes. If it uses more than 64 MB on the actual device, the OS will very likely just terminate it. In the simulator on the other hand, your app might use lots more memory without a problem.

Upvotes: 0

Related Questions