linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Disposal of internal resources which liblinpho


From: Krunal Patil
Subject: Re: [Linphone-developers] Disposal of internal resources which liblinphone uses
Date: Thu, 23 Dec 2021 18:38:19 +0530

Hi All,
Please reply back if anyone knows the way to handle this memory leak. Ideally, this should be handled by liblinphone. I am quite surprised to see that it has so many memory leaks. While development I have referred Linphone-desktop code base, which I consider to be a standard code.

Thanks and regards,
Krunal Patil


On Tue, Dec 21, 2021 at 10:07 PM Krunal Patil <krunal.patil@quantiphi.com> wrote:
Hi All,
While performing a video call using liblinphone, I have observed a lot of memory leak. Heap memory is full of various objects from various DLLs (belcard, belr, bellesip, liblinphone). Is there any way to minimize this. Any directions would be appreciated.

Thanks and regards,
Krunal Patil.

On Mon, Dec 20, 2021 at 10:41 PM Krunal Patil <krunal.patil@quantiphi.com> wrote:
Hello all,

I am developing a c++ application using liblinphone to perform a video call. After successfully performing a video call, when I try to shutdown the application and check memory usage right before returning from main function, I can see that application's memory usage is around 15MB and heap  memory is 1MB. Most of this memory is occupied by DLLs like belr.dll and belle-sip.dll etc. 

Prior to shutting-down application I terminate all the calls, stop the core and stop the iterate.

Is there any way through which we can dispose all the resources which linlinphone uses internally?

Thanks and regards,
Krunal Patil

This message contains information that may be privileged or confidential and is the property of the Quantiphi Inc and/or its affiliates. It is intended only for the person to whom it is addressed. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety

reply via email to

[Prev in Thread] Current Thread [Next in Thread]