Game Development Community

EXC_BAD_ACCESS

by Matthew M. White · in iTorque 2D · 05/05/2010 (10:12 am) · 6 replies

Hey guys,

We currently have 2 apps on the App Store made with Torque.
Both seem to quit with EXC_BAD_ACCESS errors.
This shows up in the iPhone's crash logs.

They're still getting accepted, but I'm worried that they won't if someone at Apple notices this stuff.
Any ideas on what's causing it and how I might fix it?

Thanks!

#1
05/05/2010 (10:31 am)
This error says nothing actually.
Just means access violation

Though commonly I would first check if it ran out of memory.
On pre 3GS devices you realistically have 25mb perhaps 30mb of RAM till you run into the wall where it gets killed.
#2
05/05/2010 (10:35 am)
Ah, I can probe for a more specific error when I'm at the design machine later.

This actually pops up only when the program is MANUALLY killed, ie: with the home button.

Doesn't seem to happen on its own.
#3
05/05/2010 (10:56 am)
if it happens when killed manually check out the other thread on exactly this matter on more insight.
#4
05/05/2010 (12:03 pm)
Hmm, I don't mean to be repetitive but it seems like there are dozens of threads on this exact issue. I'll try some of the things that I've been told in them (removing DSO's, checking targets, checking to ensure common and game are compiled) though .. I think I've been doing all of those things thus far.

#5
05/05/2010 (12:31 pm)
Can only remember a single one in relation to crash on quit actually.

Most others are for this error on startup and are caused by incomplete / incorrect project structures.
#6
05/05/2010 (1:31 pm)
A recent one on crash on quit suggests...

04/10/2010 (12:30 pm)
The problem seems to have gone away after I manually set these flags:
compressPVR = "1";
optimised = "1";

in the Datablocks file.

I hope this fixes the problem. Will get back to you.