Crashes in libred5streaming.so

[raoneel]

Randomly, we are seeing crashes in libred5streaming.so on Android. They appear to be happening after the stream is running for 30 seconds or so. And sometimes they happen during the subscribe() process. It is hard to re-create. I've attached two dumps below:

Device: Pixel 2
Android P

Crash 1
09-23 00:42:35.990 5797 6224 D R5Stream: Bitrate: 819.626257331075
09-23 00:42:35.990 5797 6224 D R5Stream: Packet count: 567.2154114494518
09-23 00:42:37.991 5797 6224 D R5Stream: network
09-23 00:42:37.991 5797 6224 D R5Stream: Bitrate: 825.5378916425743
09-23 00:42:37.991 5797 6224 D R5Stream: Packet count: 571.3065079197561
09-23 00:42:39.250 6346 6252 F google-breakpad: Microdump skipped (uninteresting)
09-23 00:42:39.276 5797 6252 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
09-23 00:42:39.276 5797 6252 W google-breakpad: Chrome build fingerprint:
09-23 00:42:39.276 5797 6252 W google-breakpad: 69.0.3497.100
09-23 00:42:39.276 5797 6252 W google-breakpad: 349710052
09-23 00:42:39.276 5797 6252 W google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
09-23 00:42:39.280 5797 6252 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xd3500000 in tid 6252 (Thread-25), pid 5797 (m.area120.bento)
09-23 00:42:39.395 6350 6350 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-23 00:42:39.399 939 939 I /system/bin/tombstoned: received crash request for pid 6252
09-23 00:42:39.402 6350 6350 I crash_dump32: performing dump of process 5797 (target tid = 6252)
09-23 00:42:39.417 6350 6350 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-23 00:42:39.417 6350 6350 F DEBUG : ABI: 'arm'
09-23 00:42:39.417 6350 6350 F DEBUG : pid: 5797, tid: 6252, name: Thread-25 >>> com.example.red5test <<<
09-23 00:42:39.417 6350 6350 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xd3500000
09-23 00:42:39.417 6350 6350 F DEBUG : r0 0000007e r1 00007e9c r2 00000fed r3 00000067
09-23 00:42:39.417 6350 6350 F DEBUG : r4 00000000 r5 00001008 r6 c41837f0 r7 bc615eb0
09-23 00:42:39.417 6350 6350 F DEBUG : r8 80000000 r9 c15ad284 r10 d34ffe00 r11 c14def58
09-23 00:42:39.417 6350 6350 F DEBUG : ip d34ffffd sp bd8ff450 lr c12fc384 pc c12fc3b0
09-23 00:42:39.419 6350 6350 F DEBUG :
09-23 00:42:39.419 6350 6350 F DEBUG : backtrace:
09-23 00:42:39.419 6350 6350 F DEBUG : #00 pc 0025a3b0 /data/app/com.example.red5test-_c6LBqsQEFleVR40Z8U-Tw==/lib/arm/libred5streaming.so (decode_ics.constprop.22+4124)
09-23 00:42:39.991 5797 6224 D R5Stream: network
09-23 00:42:39.991 5797 6224 D R5Stream: Bitrate: 831.4727472977771
09-23 00:42:39.991 5797 6224 D R5Stream: Packet count: 575.4136745243505

Crash 2
09-25 12:19:52.391 17374 17374 I crash_dump32: performing dump of process 15579 (target tid = 17289)
09-25 12:19:52.410 17374 17374 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-25 12:19:52.410 17374 17374 F DEBUG : ABI: 'arm'
09-25 12:19:52.410 17374 17374 F DEBUG : pid: 15579, tid: 17289, name: Thread-122 >>> com.example.red5test <<<
09-25 12:19:52.410 17374 17374 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xabc80000
09-25 12:19:52.410 17374 17374 F DEBUG : r0 abc76120 r1 abc7ffe9 r2 5f1c957a r3 00000024
09-25 12:19:52.410 17374 17374 F DEBUG : r4 abc3e980 r5 ffff88a7 r6 abb8985c r7 00004f7c
09-25 12:19:52.410 17374 17374 F DEBUG : r8 c0f66d0c r9 c0f65540 r10 c54b9fb0 r11 c0f65540
09-25 12:19:52.410 17374 17374 F DEBUG : ip 20000000 sp aa27ae68 lr c0c01821 pc e741cf70
09-25 12:19:52.417 17374 17374 F DEBUG :
09-25 12:19:52.417 17374 17374 F DEBUG : backtrace:
09-25 12:19:52.417 17374 17374 F DEBUG : #00 pc 00019f70 /system/lib/libc.so (__memcpy_base+248)
09-25 12:19:52.417 17374 17374 F DEBUG : #1 pc 0007e81d /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (flip_buffers+72)
09-25 12:19:52.417 17374 17374 F DEBUG : #2 pc 0007eab1 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (rtsp_parse_response+296)
09-25 12:19:52.417 17374 17374 F DEBUG : #3 pc 0007b835 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (conn_read_done+184)
09-25 12:19:52.417 17374 17374 F DEBUG : #4 pc 002fed44 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (uv__read+924)
09-25 12:19:52.417 17374 17374 F DEBUG : #5 pc 002ff0bc /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (uv__stream_io+288)
09-25 12:19:52.417 17374 17374 F DEBUG : #6 pc 00304e6c /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (uv__io_poll+1776)
09-25 12:19:52.417 17374 17374 F DEBUG : #7 pc 002f42f0 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (uv_run+144)
09-25 12:19:52.417 17374 17374 F DEBUG : #8 pc 0007b32d /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (connect_client+76)
09-25 12:19:52.417 17374 17374 F DEBUG : #9 pc 0007b5af /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (start_client+70)
09-25 12:19:52.417 17374 17374 F DEBUG : #10 pc 00077bd7 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (start_stream_async+110)
09-25 12:19:52.417 17374 17374 F DEBUG : #11 pc 002f23e4 /data/app/com.example.red5test-CPUZTUt7sUEDoAP0WZVMGw==/lib/arm/libred5streaming.so (uv__thread_start+60)
09-25 12:19:52.417 17374 17374 F DEBUG : #12 pc 000636a5 /system/lib/libc.so (__pthread_start(void*)+22)
09-25 12:19:52.417 17374 17374 F DEBUG : #13 pc 0001dff9 /system/lib/libc.so (__start_thread+24)

[HoldenMills]

Hello Neel,

Please submit a ticket to our support team using this link: https://red5pro.zendesk.com/hc/en-us/requests/new. As this is a random crash, any additional details and specific reproduction steps would be appreciated. Our support desk is the best way to ensure that your issue does not get lost.

Cheers,
Holden