All geek questions in one place

Crashlytics: "Crashed: NSOperationQueue 0x ... :: NSOperation 0x ..." - EXC_BAD_ACCESS KERN_INVALID_ADDRESS

I got some crashlytics crashes that I don’t understand at all, here is the thread crash log that crashed:

enter image description here

I do not find any hints of my code, and it does not play or does not occur only on certain devices. According to Crashlytics, this is not a problem with RAM or disk space, so I am really helpless here.

Does anyone have any clues with this glass?

+6
source share
1 answer

I have some thoughts:

  • The second line of the first line is iOS's way of saying what went wrong. It reads: EXC_BAD_ACCESS KERN_INVALID_ADDRESS . This is a Bad access error.
  • You are trying to _dealloc something, according to the stack trace list, [_queueForDealloc:] . Using the iOS ARC (Automatic Resource Counting) system, things in Xcode cannot call alloc or release because it allocates memory and automatically frees it. This technology was released with iOS 5.

My hunch is that the compiler really doesn't like this [_queueForDealloc:] method, which you could call, or you are trying to dealloc something that was already dealloc 'ed. (See Third -[_PFArray dealloc] : Call -[_PFArray dealloc] .)

In any case, this is a bad access error. Check that you are freeing and whether you should release it.

+2
source

Source: https://habr.com/ru/post/986085/

More articles:


All Articles