[asterisk-bugs] [JIRA] (ASTERISK-20765) Memory Leak in chan_sip with TLS enabled clients

[Rusty Newton (JIRA)]

Rusty Newton created ASTERISK-20765:
---------------------------------------

             Summary: Memory Leak in chan_sip with TLS enabled clients
                 Key: ASTERISK-20765
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20765
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Channels/chan_sip/TCP-TLS
    Affects Versions: 1.8.18.0
         Environment: Ubuntu 12.04 LTS / Asterisk 1.8.18 via SVN branch
            Reporter: deti


Since we have enabled TLS for most of our 200+ clients (Snom 360) the Asterisk process faces a serious memory leak that consumes about 2GB RAM per day.
With memory debugging enabled you can see:

10399843 bytes in 11893 allocations in file 'chan_sip.c'

Most of the allocations seem to come from line 12089:
       342 bytes allocated in         copy_request at line 12089 of chan_sip.c
       702 bytes allocated in         copy_request at line 12089 of chan_sip.c
      1041 bytes allocated in         copy_request at line 12089 of chan_sip.c
       857 bytes allocated in         copy_request at line 12089 of chan_sip.c
       700 bytes allocated in         copy_request at line 12089 of chan_sip.c
       702 bytes allocated in         copy_request at line 12089 of chan_sip.c
       847 bytes allocated in         copy_request at line 12089 of chan_sip.c
       702 bytes allocated in         copy_request at line 12089 of chan_sip.c
      1044 bytes allocated in         copy_request at line 12089 of chan_sip.c
       850 bytes allocated in         copy_request at line 12089 of chan_sip.c
       342 bytes allocated in         copy_request at line 12089 of chan_sip.c

... and my educated guess is that comes from sip_tls_read. It seems that the reqcpy created in line 2580 does not get freed properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira