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
PJSIP will use some memory while it's loaded, even if nothing is going
on. The PJSIP allocations there don't seem alarming.
json.c is using an abnormally large amount of memory, though stasis uses
JSON under the hood so that may be the ultimate culprit. You also didn't
answer the previous
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.
rasterisk -x "core show channels count"
43 active channels
29 active calls
7260 calls processed
time rasterisk -x "memory show summary" | sort -n | tail
I think PJSIP never releases memory
This Is without any open calls.
Every command is very slow.
rasterisk -x "memory show allocations" |sort -t" " -n -k1 | tail -20
25192 bytes allocated by sip_options_contact_statuses_alloc() line
415 of res_pjsip/pjsip_options.c
25216 bytes
