Android: on call end the memory claimed by SDK is not deallocated

Open

#305 opened on May 28, 2021 1 comment 0 reactions 3 assignees View on GitHub

@jsaurezlee-msft is already working on this.

Since Jul 19, 2021.

Assessment

This issue has not been assessed yet.

ADO Linked Android Bug Calling

Describe the bug

On call end, the application memory usage is not same as before starting call.

Application memory usage:
Before starting call - 150 mb
On start call - 240 mb
After call end - 182 mb

Tested on azure-communication-calling-1.0.0-beta.1.aar

Disposing call agent & call client to cleanup memory.

return call.hangUp(HangUpOptions()).thenRun {
            callAgent.close()
            callClient.close()
            call = null
        }

To Reproduce
Steps to reproduce the behaviour:

Expected behavior
After call end, the memory claimed by application may be equal to before call.

Desktop (please complete the following information):

Smartphone (please complete the following information):

No contributing guide indexed for this repository

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.