objc_release EXC_BAD_ACCESS (KERN_INVALID_ADDRESS)

Question

Created Nov ’23

Replies 2

Boosts 0

Participants 2

Hi, I've encountered this error on my app on crashlytics with the following stack trace, and I don't know what may be happening and how to prevent it.

Crashed: com.apple.root.user-initiated-qos
0  libobjc.A.dylib                0x2470 objc_release + 16
1  libsystem_blocks.dylib         0x1834 _Block_release + 184
2  libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
3  libdispatch.dylib              0x13568 _dispatch_root_queue_drain + 640
4  libdispatch.dylib              0x13c38 _dispatch_worker_thread2 + 172
5  libsystem_pthread.dylib        0x4e48 _pthread_wqthread + 224
6  libsystem_pthread.dylib        0x49f0 start_wqthread + 8

Boost

Answer 1

DTS Engineer OP

Apple

Nov ’23

What’s happening here is that Dispatch has run a block on a queue and is in the process of releasing that block. Sometimes has corrupted the block’s state which is causing that release to crash. This is commonly an over releases, but there are a variety of other potential causes.

Problems like this are very hard to fix without being able to reproduce them. My advice is that you apply the standard memory debugging tools to see if you can make it reproduce in your office.

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

0

Answer 2

cnx-caiobarroso OP

Nov ’23

I see, I'll take a look at the post you mentioned, thank you for the quick response.

0