[asterisk-bugs] [JIRA] (ASTERISK-28064) Memory leak issue in json.c, endpoints.c and stasis_channels.c While using AMI

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28064:
--------------------------------------

    Assignee: mohit dhiman  (was: Unassigned)
      Status: Waiting for Feedback  (was: Triage)

We don't support old versions, and I wouldn't foresee any individual on here going through all the changes between your old version and current looking for things that may have fixed it. If someone did the change it is possible they'd remember a specific one, but that's about it.

> Memory leak issue in json.c, endpoints.c and stasis_channels.c While using AMI
> ------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28064
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28064
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.16.0
>         Environment: Centos 7
>            Reporter: mohit dhiman
>            Assignee: mohit dhiman
>              Labels: endpoints.c, json.c, memory, stasis_channels.c
>         Attachments: memory_show_summary_memory_leak.txt, memory_show_summary_normal_case.txt
>
>
> I am using Asterisk through AMI and at a time call flow is around 250 calls at any time, now every 1 and half day later asterisk resource memory tends to increase very high because of which alot of AMI disconnection is happening.
> when i executed command 'memory show summary' during a normal case and high memory usage case i found few files that were allocated high amount of memory like:
> high memory case:
> json.c   351997999 bytes
> endpoints.c  3063068552 bytes
> stasis_channels.c  658183761 bytes
> normal case:
> json.c 600 bytes
> endpoints.c 600872 bytes
> stasis_channels.c  42317640 bytes



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