[asterisk-bugs] [JIRA] (ASTERISK-28609) Memory Leak in res_rtp_asterisk.c

Ted G (JIRA) noreply at issues.asterisk.org
Tue Dec 17 16:30:32 CST 2019


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

Ted G commented on ASTERISK-28609:
----------------------------------

I thought it should closely match the number of channels but I guess that's not right?

I guess I miss-understood what Corey was getting at when he asked for the same information and asked:

"How many channels were active when you retrieved this information? Please post the complete output of asterisk CLI memory show allocations res_rtp_asterisk.c and tell us how many channels were active at the time of retrieval."

If everyone thinks the patch is the answer, then I'm OK to close the issue out.  If memory goes crazy again I can reopen. Will the patch be in the next version?

> Memory Leak in res_rtp_asterisk.c
> ---------------------------------
>
>                 Key: ASTERISK-28609
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28609
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 16.3.0
>            Reporter: Ted G
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: fax, patch
>         Attachments: ASTERISK-28609-1.patch, frame-malloc-debug.patch, leak.txt, mem-20191216.txt
>
>
> Hello,
>   There appears to be a memory leak in frame.c.
> Sometimes I received these errors in my logs:
> [Nov  5 21:14:49] WARNING[14918][C-00028a27]: file.c:258 ast_writestream: Translated frame write failed
> I believe this happenes because of some issues between my carrier and the asterisk system and most of the time these errors are not frequent.
> However sometimes these errors are produced thousands of times per day and when that happens the memory usage for asterisk shoots up and never recovers:
> ...
>    1073986 bytes in       5455 allocations in file xmldoc.c
>    1327380 bytes in       1819 allocations in file chan_sip.c
>    1351770 bytes in        840 allocations in file res_rtp_asterisk.c
>    1707720 bytes in        105 allocations in file smoother.c
>    2409853 bytes in        255 allocations in file file.c
>    2988480 bytes in        163 allocations in file bridge_softmix.c
>    7310456 bytes in        633 allocations in file translate.c
>    7434868 bytes in       2773 allocations in file confbridge/conf_config_parser.c
>  899355372 bytes ( 899355372 cache) in    2046261 allocations in file frame.c         <----
>  933339512 bytes allocated (899355372 in caches) in 2102261 selected allocations
>  933339512 bytes in all allocations
>  934016850 bytes in all allocations and deferred free allocations
> axis/root# top -b -n 1 | grep asterisk
> 19727 root      20   0 3353860 1.314g   8256 S 111.8  2.1  16620:19 asterisk     1.3GB :(
> System uptime: 1 week, 3 days, 23 hours, 34 minutes, 42 seconds
> 1 week, 3 days worth of frame write failed error counts:
> mmdd errors
> 1027 2218
> 1028 1426
> 1029 5275
> 1030 2454
> 1031 1612
> 1101 2797
> 1102 1635
> 1103 3278
> 1104 743
> 1105 1117



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



More information about the asterisk-bugs mailing list