What's wrong with __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__

Question

Created Mar ’22

Replies 1

Boosts 0

Views 1.1k

Participants 2

0  CoreFoundation                 0x4a690 -[__NSDictionaryM setObject:forKey:] + 404
1  Luxy                           0xfe00d8 __57-[YapDatabaseViewState group_pagesMetadata_dict_deepCopy]_block_invoke + 50 (YapDatabaseViewState.m:50)
2  CoreFoundation                 0x3d130 __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 16
3  CoreFoundation                 0x53d70 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 204
4  Luxy                           0xfe0044 -[YapDatabaseViewState group_pagesMetadata_dict_deepCopy] + 54 (YapDatabaseViewState.m:54)
5  Luxy                           0xfe0150 -[YapDatabaseViewState copyWithZone:] + 66 (YapDatabaseViewState.m:66)
6  Luxy                           0xfd7c88 -[YapDatabaseViewConnection getInternalChangeset:externalChangeset:hasDiskChanges:] + 288 (YapDatabaseViewConnection.m:288)
7  Luxy                           0xf38774 -[YapDatabaseAutoViewConnection getInternalChangeset:externalChangeset:hasDiskChanges:] + 138 (YapDatabaseAutoViewConnection.m:138)
8  Luxy                           0xf73374 __64-[YapDatabaseConnection getInternalChangeset:externalChangeset:]_block_invoke + 3880 (YapDatabaseConnection.m:3880)
9  CoreFoundation                 0x3d130 __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 16
10 CoreFoundation                 0x53d70 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 204
11 Luxy                           0xf72cf0 -[YapDatabaseConnection getInternalChangeset:externalChangeset:] + 3870 (YapDatabaseConnection.m:3870)
12 Luxy                           0xf7050c -[YapDatabaseConnection postReadWriteTransaction:] + 2945 (YapDatabaseConnection.m:2945)
13 Luxy                           0xf6e848 __44-[YapDatabaseConnection readWriteWithBlock:]_block_invoke_2 + 2022 (YapDatabaseConnection.m:2022)
14 libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
15 libdispatch.dylib              0x460dc _dispatch_lane_barrier_sync_invoke_and_complete + 52
16 Luxy                           0xf6e788 __44-[YapDatabaseConnection readWriteWithBlock:]_block_invoke + 2014 (YapDatabaseConnection.m:2014)
17 libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
18 libdispatch.dylib              0x460dc _dispatch_lane_barrier_sync_invoke_and_complete + 52
19 Luxy                           0xf6e688 -[YapDatabaseConnection readWriteWithBlock:] + 2040 (YapDatabaseConnection.m:2040)
20 Luxy                           0x10bed0 -[MomentGetByUinBusiness parseGetMomentByTypeDataRsp:type:] + 108 (MomentGetByUinBusiness.mm:108)
21 Luxy                           0x10bcec __69-[MomentGetByUinBusiness handleMomentsWithSendMsg:receiveMsg:result:]_block_invoke + 79 (MomentGetByUinBusiness.mm:79)
22 libdispatch.dylib              0x631a4 _dispatch_call_block_and_release + 24
23 libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
24 libdispatch.dylib              0x3f14c _dispatch_lane_serial_drain$VARIANT$armv81 + 604
25 libdispatch.dylib              0x3fc04 _dispatch_lane_invoke$VARIANT$armv81 + 388
26 libdispatch.dylib              0x495dc _dispatch_workloop_worker_thread + 616
27 libsystem_pthread.dylib        0x4e84 _pthread_wqthread + 284
28 libsystem_pthread.dylib        0x49f0 start_wqthread + 8

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’22

What's wrong with __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__

Nothing is wrong with that. It’s a special symbol deliberately inserted by the NSDictionary authors to make it clear that, if your process crashes with that in the backtrace, it’s not the fault of NSDictionary but rather the block that you told NSDictionary to call. In this case your -[YapDatabaseConnection getInternalChangeset:externalChangeset:] method (frame 11) called -enumerateKeysAndObjectsWithOptions:usingBlock: (frame 10) with a block (frame 8). That block did some stuff that eventually crashed the process.

As to what caused that, it’s hard to say. I may be able to offer more insight if you post a full crash report. See Posting a Crash Report for advice on how to do that.

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

0