Re: memory leak?
[email protected] Thu, 13 Jul 2023 20:15:52 -0400
| Newsgroups | gmane.comp.telephony.pbx.asterisk.user |
|---|---|
| Message-ID | <[email protected]> |
On 7/13/2023 8:10 PM, Federico wrote:
>
> This is asterisk 16.30.1, after 1 hours, with 17 contacts, yet we need
> to kill it every two hours because it stops processing calls.
>
> ...
>
> 160393938 bytes in 2227792 allocations in file stasis_message.c
>
> 440540801 bytes in 8647565 allocations in file json.c
>
> 3011728948 bytes in 2923317 allocations in file stasis_channels.c
>
> 3750730746 bytes allocated (69073 in caches) in 16358993 selected
> allocations
>
> 3750730746 bytes in all allocations
>
> 3751451731 bytes in all allocations and deferred free allocations
>
440 MB of usage in json.c and 3 GB in stasis_channels.c look suspicious.
Are you using the JSON_DECODE function by chance? There was a memory
leak bug in it fixed a while back[1]. However, it was not cherry picked
to the 16 branch as that was after 16 went out of regular support. So if
you're using this function, you have a buggy version that is likely
responsible for your leak. You can fix this by upgrading to a supported
version of Asterisk.
[1] https://gerrit.asterisk.org/c/asterisk/+/19477
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users