There are a few threads on SO regarding this issue but none is answered really.
Apparently it has something to do with AVAudioPlayer but that's about it. No one seems to be able to point out what exactly to fix.
In my case, I get that error message but everything works fine. The audio file gets played, no crash, nothing. Anyhow I'd still like to know why I'm getting that error message and eventually, eliminate it completely.
This error doesn't show up often at all. It almost never happens but maybe once every 40 tries I'd get one... it is so random so I'm not sure what to do about it.
Can someone please help me?
Related
I have a problem with my Arc Map which is my records(complications) keep getting deleted somehow and I have no idea how it happens. so I wanted to ask is there any way to find out how this problem keep happening to me? I wish all the best to you.
I tried to see logs but I saw nothing of importance to my problem
I've not worked on this project in quite some time.. When I left it some time in the iOS 8s it ran just fine, however.. on the latest XCode I'm getting many inconsistent EXC_BAD_ACCESS crashes. Now afaik it's requiring a deallocated object. However, the error is lacking where to look. This is quite a big project and like I say, the errors are inconsistent.
I've tried enabling zombie objects, as well as passing it as a starting parameter. However, this is leading me to no joy. I'm expecting something in the debug console with zombies enabled, is this right?
If anyone has any tips on how to find an easier way to debug this, as opposed to tinkering with everything and hoping it works..
EXC_BAD_ACCESS just means that your app is trying to access an invalid memory address. While it is oft caused be a deallocated object, that isn't always the case.
When the app crashes, there should be a crash log or backtrace. Post it as that'll provide clues.
Lovely; a crash entirely in framework code. Seeing as how it is SceneKit that is crashing, I would suggest replacing any graphic assets with new ones and see if that fixes it (even if it doesn't look right). Then check to make sure all of your geometries and layouts are correct.
Have you tried adding a global Exception or Symbolic breakpoint? Those usually help me 99% of the time when I encounter issues without any sort of backtrace.
I'm working on a tweak using captainhook.
I did something like:
[self.delegate somemessage];
//the message is a private api. I don't know its implementation detail.
and then the app used up a lot of system resources and got killed minutes later.
the problem is none of logs, errors or exceptions can be found in console. there is only a LowMemory crash report.
I'd like to know what's the possible causes of that, how can I deal with it?
I dont have even the least idea where to start to debug it…
We've got an application that on rare occasions crashes with the error:
Missing proxy for identifier IBFilesOwner
We understand it to be implying that it can't find File's Owner for one of our nibs (xibs) but we've been through and confirmed they all have valid ones set.
There's practically zero on Google, can anyone offer any suggestions?
Thanks.
Hey I had the same problem and it turned out that I was doing some threading and I was executing code that should be on the main thread on another thread.
I don't know what you're doing in your app, but hopefully that might give you a clue.
If you share some code we can try and figure out what's going on.
I wrote an entire app, and I was just about to submit it to the app store, and in my final testing, I went back and added a few releases to ensure proper memory management was observed. And since then, I keep getting these random crashes. I've tried removing some or all of the release calls, I've tried retaining objects. I cleaned the project. I used NSZombieEnabled and that also is not helping. All this to not avail.
Most of the time, the console says provides no help. Usually the app loads, I put NSLogs in viewDidLoad, viewDidAppear, and viewWillAppear, and they all show up in the console, then it crashes.
Sometimes I also get EXC_BAD_ACCESS (and I know what that means). But its occurring randomly. So this doesn't make sense to me. Thanks for any help possible. I've written this whole app, and spent months on it. So I'm really stuck. Thank you.
Have you tried Build --> Analyze? It will search your code for leaks and other useful things you might have missed. Try that and see if it finds anything for you.
I agree with Rudy. It sounds like you're releasing something that is still in use. I would go back to the version that was working and start adding the releases one at a time til it causes the crash. Slow but effective debugging.
When you say that you "sometimes" get EXC_BAD_ACCESS, what do you get the rest of the time? Where does the crash stack indicate you're crashing? What messages do you get?
Random crashes usually indicate a timing problem. A common cause is accessing things on multiple threads. Are you? It can also mean timing differences based on network traffic.
Make sure the console doesn't indicate an exception rather than a memory violation. Usually there's something in the console that will be useful.