[asterisk-bugs] [JIRA] (ASTERISK-29274) Possible Memory Leak in PJSIP TLS Transport

[Troy Bowman (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253690#comment-253690 ] 

Troy Bowman commented on ASTERISK-29274:
----------------------------------------

It looks like this may be a PJSIP issue that was fixed in 2.10.

https://trac.pjsip.org/repos/ticket/2244

I'll see if I can upgrade and verify.


> Possible Memory Leak in PJSIP TLS Transport
> -------------------------------------------
>
>                 Key: ASTERISK-29274
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29274
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.8.0
>         Environment: Asterisk 16.8-cert5 using pjproject-2.9 on Gentoo on QEMU KVM
>            Reporter: Troy Bowman
>            Severity: Major
>
> Last Saturday morning, I enabled the TLS transport in my PJSIP configuration and turned on SIPS for our Polycom phones and our provider trunks. I wanted to test TLS while we have a lower weekend call volume. 
>  Things worked well, aside from some non-fatal errors. However, I am concerned that memory usage gradually increases with this change.
> Please see my community post for graphs and the steps I took to find out what was filling up memory unnecessarily:
> https://community.asterisk.org/t/pjsip-tls-transport-memory-leak/87363
> I have since disabled TLS on all of my Polycom phones and trunks, and it is behaving normally as it did before.  TLS is the only difference in this change, so I am pretty sure there is an issue with the storage of client certificates and CA certificates.
> I can provide one of the 128M memory page dumps by other means if it is desired.



--
This message was sent by Atlassian JIRA
(v6.2#6252)