[BUG] Occasional crash/video failure when using DeviceManager #1537
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
In the azure-communication-calling library, sometimes when getting cameras from the DeviceManager, the app crashes. Other times, we get the list of cameras just fine, but then the VideoStreamRenderer doesn't fire its onFirstFrameRendered() event and the VideoStreamRendererView doesn't show video.
This bug is tricky and doesn't always happen, but disposing and creating a new CallClient several times in a row usually triggers it (about 1 in 10 restarts).
Exception or Stack Trace
There's no exact exception, but adb logcat produces a variety of logs right when the crash happens or video fails to start.
App crash 1:
App crash 2:
App crash 3:
App crash 4:
App doesn't crash but video fails to render 1:
App doesn't crash but video fails to render 2:
App doesn't crash but video fails to render 3:
To Reproduce
Code Snippet
I forked the videoCallingQuickstart example, and I've modified it to have a button that easily lets me dispose and re-create the SDK (CallClient, CallAgent, DeviceManager, etc.). I also modified it to allow me to toggle video on and off without being inside a call. If you restart the SDK enough times and keep toggling video on and off, the app eventually crashes or video doesn't render. See the
videoCallingQuickstart
project here: https://github.com/JasonWeinzierl/communication-services-android-quickstartsExpected behavior
Video should always render successfully.
Screenshots
N/A
Setup (please complete the following information):
Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: