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
We are using the t_uac_dlg function through a UDP MI Datagram to create local SIP/TCP requests. We are seeing a memory leak of increasing shared Memory usage, which is increasing at the same rate as tcp connections are created (tested under 4.0.1 and 4.3.1).
We are using the t_uac_dlg function through a UDP MI Datagram to create local SIP/TCP requests. We are seeing a memory leak of increasing shared Memory usage, which is increasing at the same rate as tcp connections are created (tested under 4.0.1 and 4.3.1).
After looking at the memory dump and investigating the source, I guess that the memory leak is created, when the
is set. This seems to be set by:
only, which we are using heavily.
Can someone please give me a hint, where to search for the memory leak. My guess is that:
modules/mi_datagram/datagram_fnc.c:489
the handler is not correctly freed up in the async reply case.
Thank you!
Greetings
The text was updated successfully, but these errors were encountered: