App crash reports from iOS 15

Greetings. We have noticed a few crash reports, majorly from devices running iOS 15 and rarely from iOS 14.4.1.

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000181ef1a54
Crashed Thread:  16

Crashed Thread:

Thread 16 Crashed:
0   libnetwork.dylib                0x0000000181ef1a54 0x181c02000 + 3078740 ( + 2112)
1   libnetwork.dylib                0x0000000181ef1964 0x181c02000 + 3078500 ( + 1872)
2   libnetwork.dylib                0x0000000181ef0ca8 0x181c02000 + 3075240 ( + 652)
3   libusrtcp.dylib                 0x0000000184e9c400 0x184e98000 + 17408 ( + 636)
4   libusrtcp.dylib                 0x0000000184ec10d0 0x184e98000 + 168144 ( + 156)
5   libusrtcp.dylib                 0x0000000184ee8290 0x184e98000 + 328336 ( + 3180)
6   libusrtcp.dylib                 0x0000000184ea7b5c 0x184e98000 + 64348 ( + 376)
7   libboringssl.dylib              0x0000000199f3bdec 0x199f2f000 + 52716 ( + 176)
8   libboringssl.dylib              0x0000000199f3b668 0x199f2f000 + 50792 ( + 356)
9   libboringssl.dylib              0x0000000199f321c4 0x199f2f000 + 12740 ( + 40)
10  libboringssl.dylib              0x0000000199f564d8 0x199f2f000 + 160984 (BIO_read + 60)
11  libboringssl.dylib              0x0000000199f73aec 0x199f2f000 + 281324 ( + 388)
12  libboringssl.dylib              0x0000000199f73bd4 0x199f2f000 + 281556 ( + 148)
13  libboringssl.dylib              0x0000000199f8041c 0x199f2f000 + 332828 ( + 364)
14  libboringssl.dylib              0x0000000199f80268 0x199f2f000 + 332392 (SSL_peek + 92)
15  libboringssl.dylib              0x0000000199f34bb4 0x199f2f000 + 23476 (boringssl_session_read + 264)
16  libboringssl.dylib              0x0000000199f3c7ac 0x199f2f000 + 55212 ( + 396)
17  libboringssl.dylib              0x0000000199f3d75c 0x199f2f000 + 59228 ( + 320)
18  libusrtcp.dylib                 0x0000000184eb8594 0x184e98000 + 132500 ( + 528)
19  libusrtcp.dylib                 0x0000000184ea71bc 0x184e98000 + 61884 ( + 100)
20  libnetwork.dylib                0x00000001820e226c 0x181c02000 + 5112428 ( + 9896)
21  libnetwork.dylib                0x00000001820dfadc 0x181c02000 + 5102300 ( + 300)
22  libnetwork.dylib                0x00000001820ded68 0x181c02000 + 5098856 ( + 68)
23  libdispatch.dylib               0x0000000180ce8094 0x180c84000 + 409748 ( + 16)
24  libdispatch.dylib               0x0000000180cbfab8 0x180c84000 + 244408 ( + 432)
25  libdispatch.dylib               0x0000000180cd116c 0x180c84000 + 315756 ( + 1560)
26  libdispatch.dylib               0x0000000180cc5094 0x180c84000 + 266388 ( + 1640)
27  libdispatch.dylib               0x0000000180ccd8e0 0x180c84000 + 301280 ( + 608)
28  libsystem_pthread.dylib         0x00000001dc2f7e10 0x1dc2f6000 + 7696 (_pthread_wqthread + 284)

Complete Crash Report:

Complete Crash Report

Any help with understanding the cause of this issue is greatly appreciated.

Post not yet marked as solved Up vote post of rishi_menon Down vote post of rishi_menon
90 views
Posted by
rishi_menon
Reply
Add a Comment

Replies

Consider this:

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000181ef1a54
Crashed Thread:  16

The EXC_BREAKPOINT suggests that the process deliberately crashed due to a trap.

Now this:

Thread 16 Crashed:
0   libnetwork.dylib … 0x181c02000 + 3078740 ( + 2112)
1   libnetwork.dylib … 0x181c02000 + 3078500 ( + 1872)
2   libnetwork.dylib … 0x181c02000 + 3075240 ( + 652)
3   libusrtcp.dylib  … 0x184e98000 + 17408 ( + 636)

Your crash report has no symbols but I was able to add them myself, resulting in this:

Thread 16 Crashed:
0   libnetwork.dylib … nw_mem_slab_create + 2112
1   libnetwork.dylib … nw_mem_slab_create + 1872
2   libnetwork.dylib … nw_mem_cache_alloc + 652
3   libusrtcp.dylib  … nw_protocol_tcp_get_slab_frame + 636

That’s very interesting. Something has gone horribly wrong with the memory allocator used by user-space TCP stack. This is not simply a case of it being out of memory, but rather a trap caused by some internal inconsistency.

It’s possible that this is caused by a memory management issue on your part. I encourage you to test your app with the standard memory debugging tools.

If that doesn’t turn something up, please file a bug about this and then post your bug number here.

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

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment