Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Android] - API 21 and 22, crash on call.startVideo

Abierto
#326 1 comentario 0 reacciones 1 asignado Ver en GitHub

@kagbakpem ya está trabajando en esto.

Desde el 2/7/2021.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

ADO Linked Android Bug Calling

Describe the bug
Start video cause crash for application on device using Android API 21 and 22

To Reproduce
Steps to reproduce the behavior:

  • Created emulator using API 21 or 22
  • Mapped MAC camera to android device emulator
  • On turn camera on, call to call.startVideo, application crashed

Desktop (please complete the following information):

  • OS: MAC

Smartphone (please complete the following information):

  • Device: Pixel 3 API 21 & 22

Additional context

Logs
Log:
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_QemuDevice: connectDevice: Connected to device '0x8020000005ac8514'
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: setCallbacks: 0xb7582030, 0xb75823e0, 0xb75824f0, 0xb75829e0 (0xb5cee6a0)
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: enableMessage: msg_type = 0xc0d
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_ERROR
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_FOCUS
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_ZOOM
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_PREVIEW_METADATA
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: **** Currently enabled messages:
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_ERROR
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_FOCUS
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_ZOOM
06-30 08:05:50.897 1188-1188/? V/EmulatedCamera_CallbackNotifier: CAMERA_MSG_PREVIEW_METADATA

--------- beginning of crash

06-30 08:05:51.428 4987-5046/com.azure.android.communication.ui A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x14 in tid 5046 (Thread-321)
06-30 08:05:51.533 1182-1182/? I/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-30 08:05:51.533 1182-1182/? I/DEBUG: Build fingerprint: 'Android/sdk_google_phone_x86/generic_x86:5.1.1/LMY48X/6695563:userdebug/test-keys'
06-30 08:05:51.533 1182-1182/? I/DEBUG: Revision: '0'
06-30 08:05:51.533 1182-1182/? I/DEBUG: ABI: 'x86'
06-30 08:05:51.534 1182-1182/? I/DEBUG: pid: 4987, tid: 5046, name: Thread-321 >>> com.azure.android.communication.ui <<<
06-30 08:05:51.534 1182-1182/? I/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
06-30 08:05:51.543 1182-1182/? I/DEBUG: eax 00000000 ebx a096a3fc ecx 00000000 edx 00000000
06-30 08:05:51.543 1182-1182/? I/DEBUG: esi 9aa85010 edi 00000000
06-30 08:05:51.543 1182-1182/? I/DEBUG: xcs 00000073 xds 0000007b xes 0000007b xfs 0000011f xss 0000007b
06-30 08:05:51.543 1182-1182/? I/DEBUG: eip 9feca0fa ebp 9d101f58 esp 9d101ee0 flags 00010246
06-30 08:05:51.543 1182-1182/? I/DEBUG: backtrace:
06-30 08:05:51.543 1182-1182/? I/DEBUG: #00 pc 006180fa /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #01 pc 005fc615 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #02 pc 006bd53a /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #03 pc 0075314f /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #04 pc 00753f0a /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #05 pc 00753bb4 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #06 pc 007ed4b6 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #07 pc 007e8a69 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.543 1182-1182/? I/DEBUG: #08 pc 007e894f /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #09 pc 007e5429 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #10 pc 007e9554 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #11 pc 00822d85 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #12 pc 008187d4 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #13 pc 0081514d /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #14 pc 008154f6 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #15 pc 008bfd7d /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #16 pc 008bff6f /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #17 pc 008c047d /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #18 pc 0028252b /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #19 pc 001dfa84 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #20 pc 00153179 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #21 pc 00163cd2 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #22 pc 00163b4c /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #23 pc 000f8a47 /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #24 pc 000f81ca /data/app/com.azure.android.communication.ui-1/lib/x86/libRtmMediaManagerDyn.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #25 pc 0034b017 /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #26 pc 00390e97 /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #27 pc 00392ab8 /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.544 1182-1182/? I/DEBUG: #28 pc 00392d56 /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #29 pc 003687dd /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #30 pc 00369147 /data/app/com.azure.android.communication.ui-1/lib/x86/libACSCallingShared.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #31 pc 000a52ca /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #32 pc 000a5796 /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #33 pc 00111824 /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #34 pc 00111722 /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #35 pc 00111aec /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #36 pc 00111a9b /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #37 pc 000a52ca /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #38 pc 000a574a /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #39 pc 0010f219 /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #40 pc 0010f0de /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #41 pc 00080982 /data/app/com.azure.android.communication.ui-1/lib/x86/libskypert.so
06-30 08:05:51.545 1182-1182/? I/DEBUG: #42 pc 000211a8 /system/lib/libc.so (__pthread_start(void*)+56)
06-30 08:05:51.545 1182-1182/? I/DEBUG: #43 pc 0001c529 /system/lib/libc.so (__start_thread+25)
06-30 08:05:51.545 1182-1182/? I/DEBUG: #44 pc 000130f6 /system/lib/libc.so (__bionic_clone+70)
06-30 08:05:51.564 1182-1182/? W/libbacktrace: virtual bool Backtrace::VerifyReadWordArgs(uintptr_t, word_t*): invalid pointer 0x9f00c87e
06-30 08:05:51.640 1182-1182/? I/DEBUG: Tombstone written to: /data/tombstones/tombstone_00
06-30 08:05:51.641 1533-5108/system_process W/ActivityManager: Force finishing activity 1 com.azure.android.communication.ui/com.azure.android.communication.toolkit.presentation.MainActivity
06-30 08:05:51.650 1188-2052/? W/CameraService: Disconnecting camera client 0xb546e7b0 since the binder for it died (this pid 1188)

Device Files: Attached in bug https://skype.visualstudio.com/SPOOL/_workitems/edit/2503547

Lenguaje dominante
Sin datos de lenguaje
Estrellas
339
Forks
113
Merge medio
36 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/Communication

Todos los issues de Azure/Communication

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.