Cannot interpret crashlog _assertionFailure

Question

Thread 9 name:
Thread 9 Crashed:
0   libswiftCore.dylib            	0x0000000188d21398 _assertionFailure(_:_:file:line:flags:) + 1504 (AssertCommon.swift:132)
1   libswiftFoundation.dylib      	0x0000000188c8beec specialized static Int32._forceBridgeFromObjectiveC(_:result:) + 372 (NSNumber.swift:207)
2   HaishinKit                    	0x0000000102fbe46c VideoIOComponent.attachScreen(_:useScreenSize:) + 496 (<compiler-generated>:0)
3   HaishinKit                    	0x0000000102f7e188 closure #1 in NetStream.attachScreen(_:useScreenSize:) + 156 (NetStream+Extension.swift:18)
4   HaishinKit                    	0x0000000102f2ff7c thunk for @escaping @callee_guaranteed () -> () + 20 (<compiler-generated>:0)
5   libdispatch.dylib             	0x0000000184fbf2b0 _dispatch_call_block_and_release + 24 (init.c:1466)
6   libdispatch.dylib             	0x0000000184fc0298 _dispatch_client_callout + 16 (object.m:559)
7   libdispatch.dylib             	0x0000000184f9c344 _dispatch_lane_serial_drain$VARIANT$armv81 + 568 (inline_internal.h:2557)
8   libdispatch.dylib             	0x0000000184f9ce2c _dispatch_lane_invoke$VARIANT$armv81 + 400 (queue.c:3862)
9   libdispatch.dylib             	0x0000000184fa666c _dispatch_workloop_worker_thread + 692 (queue.c:6589)
10  libsystem_pthread.dylib       	0x00000001cd8bd5bc _pthread_wqthread + 272 (pthread.c:2436)
11  libsystem_pthread.dylib       	0x00000001cd8c086c start_wqthread + 8

Thread 10:
0   libsystem_pthread.dylib       	0x00000001cd8c0864 _pthread_dependency_fulfill_slow + 192 (pthread_dependency.c:57)

Thread 11:
0   libsystem_pthread.dylib       	0x00000001cd8c0864 _pthread_dependency_fulfill_slow + 192 (pthread_dependency.c:57)

Thread 9 crashed with ARM Thread State (64-bit):
    x0: 0x0000000282abc480   x1: 0x0000000188fe7840   x2: 0x0000000000000007   x3: 0x0000000193edad18
    x4: 0x0000000000000000   x5: 0x000000016da46630   x6: 0x0000000000000032   x7: 0x000000000000003e
    x8: 0x0000000282abc488   x9: 0xfffffffe00000000  x10: 0x0000000200000003  x11: 0x0000000000000001
   x12: 0x0000000000000003  x13: 0x000000009740682d  x14: 0x0000000097607000  x15: 0x0000000000007000
   x16: 0x0000000017600000  x17: 0x02000001000001f8  x18: 0x0000000000000000  x19: 0x0000000282abc480
   x20: 0x000000016da466c0  x21: 0x0000000188cd5688  x22: 0x0000000000000019  x23: 0x0000000000000000
   x24: 0x00000000000000cf  x25: 0x000000000000000b  x26: 0x0000000000000002  x27: 0x0000000188cd6040
   x28: 0x000000016da46700   fp: 0x000000016da467b0   lr: 0x0000000188d21398
    sp: 0x000000016da46700   pc: 0x0000000188d21398 cpsr: 0x60000000
   esr: 0xf2000001  Address size fault

When the app try to live stream on Youtube, this crash occur. Only some device experience this crash.

Thank you in advance! Tenna

2.0k

Posted by

tenna

Reply

Add a Comment

Answer 1

Consider this:

0   libswiftCore.dylib       … _assertionFailure(_:_:file:line:flags:) + 1504 (AssertCommon.swift:132)
1   libswiftFoundation.dylib … specialized static Int32._forceBridgeFromObjectiveC(_:result:) + 372 (NSNumber.swift:207)
2   HaishinKit               … VideoIOComponent.attachScreen(_:useScreenSize:) + 496 (<compiler-generated>:0)
3   HaishinKit               … closure #1 in NetStream.attachScreen(_:useScreenSize:) + 156 (NetStream+Extension.swift:18)
4   HaishinKit               … thunk for @escaping @callee_guaranteed () -> () + 20 (<compiler-generated>:0)

Frame 0 indicates that Swift has trapped due to a failed assert.

Frame 1 suggests that this is related to converting an NSNumber to an Int32. This can fail for a variety of reasons, the most obvious being that the object that’s meant to be an NSNumber isn’t, or that the resulting number is out out of bounds.

Frame 2 is some compiler generated goo within your code.

Frame 3 gives you a function name (that is, a closure within the NetStream.attachScreen(_:useScreenSize:) function) and a source file and line number (NetStream+Extension.swift:18). What does that code look like?

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

Posted by

eskimo

Add a Comment

Answer 2

Consider this:

0   libswiftCore.dylib       … _assertionFailure(_:_:file:line:flags:) + 1504 (AssertCommon.swift:132)
1   libswiftFoundation.dylib … specialized static Int32._forceBridgeFromObjectiveC(_:result:) + 372 (NSNumber.swift:207)
2   HaishinKit               … VideoIOComponent.attachScreen(_:useScreenSize:) + 496 (<compiler-generated>:0)
3   HaishinKit               … closure #1 in NetStream.attachScreen(_:useScreenSize:) + 156 (NetStream+Extension.swift:18)
4   HaishinKit               … thunk for @escaping @callee_guaranteed () -> () + 20 (<compiler-generated>:0)

Frame 0 indicates that Swift has trapped due to a failed assert.

Frame 1 suggests that this is related to converting an NSNumber to an Int32. This can fail for a variety of reasons, the most obvious being that the object that’s meant to be an NSNumber isn’t, or that the resulting number is out out of bounds.

Frame 2 is some compiler generated goo within your code.

Frame 3 gives you a function name (that is, a closure within the NetStream.attachScreen(_:useScreenSize:) function) and a source file and line number (NetStream+Extension.swift:18). What does that code look like?

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

Posted by

eskimo

Add a Comment

Cannot interpret crashlog _assertionFailure

Accepted Reply

Replies