Android: com.azure.android:azure-communication-calling failed: errno 28 No space left on device

[iaulakh]

Describe the bug
After running call for sometime, application crashes with"errno 28 No space left on device"

    --------- beginning of crash
E/AndroidRuntime: FATAL EXCEPTION: GLTextureView
    Process: com.azure.android.communication.ui, PID: 12859
    com.skype.android.video.render.EGLException: EGL error: 12291 eglCreateContext
        at com.skype.android.video.render.EGL10RenderSurface.check(EGL10RenderSurface.java:107)
        at com.skype.android.video.render.EGL10RenderSurface.create(EGL10RenderSurface.java:64)
        at com.skype.android.video.render.GLTextureView._createSurface(GLTextureView.java:270)
        at com.skype.android.video.render.GLTextureView.handleMessage(GLTextureView.java:120)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:223)
        at android.os.HandlerThread.run(HandlerThread.java:67)

To Reproduce
Steps to reproduce the behavior:

1. Start call
2. Join with 6 participants video on and 6 participants with audio only
3. Unmute all
4. After sometime application crashes with above error message

Memory while crashing:

Desktop (please complete the following information):

• OS: Android 11

Smartphone (please complete the following information):

• Device: Google Pixel 4a

https://skype.visualstudio.com/SPOOL/_workitems/edit/2540286

[jsaurezlee-msft]

AB#2540286
AB#2540280

[jaime-carpintero]

@jsaurezlee-msft based on the extra information that was provided by Inderpal, we proceed to conduct an in-depth test based on the following:

Physical device was being used (Pixel 4a)
Potential SDK version used at the time: 1.2.0-beta.2
error: No space left on device should be output on android studio's logcat
Average time to reproduce is between 30min~40min
Participants were toggling video on/off
No profiler was attached to the device
Conducting test using physical device to see if this bug is still present.

[jsaurezlee-msft]

Closing as per @jaime-carpintero investigation:

Test were conducted based on extra information provided by the user.

Test were performed with the following ACS calling SDK versions:
azure-communication-calling-1.2.0
azure-communication-calling-1.2.0-beta.2
azure-communication-calling-1.2.1-beta.1

being unable to replicate the issue described. closing issue.

Please let us know if this issue needs to be reopen.

[mariusu-msft]

Reopening based on new feedback from @iaulakh

[jaime-carpintero]

After conducting the test, by applying the code provided and being tested for a longer and short period of times the issue could not be replicated. Please feel free to re-open the issue if more details have been gathered.

Test was conducted on:
Group call using ACS calling SDK:
com.azure.android:azure-communication-calling:1.2.0-beta.2
com.azure.android:azure-communication-calling:1.2.1-beta.1

Huawei P30 Pro physical device
Pixel 4 emulated device.

Closing issue as conducting the test described above could not replicate the issue.

@jsaurezlee-msft , could you help me closing the issue please

[jsaurezlee-msft]

Closing as per @jaime-carpintero comment.

[iaulakh]

@jaime-carpintero would it be possible to reopen-github issue?