You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
See livekit/client-sdk-swift#420. I found that the same memory leak problem appears on Android for every publish -> unpublish track operation.
To Reproduce
Publish then unpublish a camera track, repeat these steps multiple times and you will see that the memory increases. The memory will be deallocated when the room is disconnected.
Expected behavior
After every camera track unpublish the memory should decrease.
@davidliu We have the same leak here, except that the native memory doesn't decrease for us even after disconnecting from room.
The reproduction step that cause the native mem leak in our case is simply trying to repeatedly create a LocalVideoTrack with a custom CameraCapturer as implemented in below function:
The memory status screenshot is here:
We can also provide a reproducible sample within LiveKit SDK sample app as well if you need.
So, please help taking a look.
Describe the bug
See livekit/client-sdk-swift#420. I found that the same memory leak problem appears on Android for every publish -> unpublish track operation.
To Reproduce
Publish then unpublish a camera track, repeat these steps multiple times and you will see that the memory increases. The memory will be deallocated when the room is disconnected.
Expected behavior
After every camera track unpublish the memory should decrease.
Screenshots

Device Info:
Additional context
See livekit/client-sdk-swift#420 (comment)
The text was updated successfully, but these errors were encountered: