objc_release crash with no indication why it happens

Hi,

I'm getting this strange crash with no indication of where it's going. I am not able to reproduce this on my devices. Any idea what could be wrong and where to look for the problem?

It looks it happens in autorelease pool cleaning in main loop, however I am not affecting it in my app - I am using ARC.

Thanks,

Jindrich

This is the classic symptom of an over-release bug. If you over release an object that’s in the autorelease pool, you won’t see the problem until the autorelease pool drains and releases its reference.

I am using ARC.

While ARC helps you avoid most over-release bugs, there’s still plenty of ways to trigger an over release in ARC code.

Or, this could just be a bug in the OS itself.

Regardless, the way forward is clear. Run your app with Zombies. That should help flush out the problem and then understand what’s going on from there. For links to the docs, see my standard memory debugging tools post.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi,

thanks for the answer. The problem is, that we are not able to simulate this. This crash never happens on our devices, but to relative big amount of customers in release build. Also the problem with Zombies enables it, that we got out of memory very quickly. We have video transmission app and that encoded frames, that are not removed from memory with zombies enabled made out of memory in seconds...

Jindrich

Also the problem with Zombies enables it, that we got out of memory very quickly.

Yeah, that makes things tricky.

Is this iOS?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

objc_release crash with no indication why it happens
 
 
Q