[Spce-user] BUG: kamailio-proxy freeing already freed pointer, called from core

[Rickey]

Good day,

 NGCP: CE mr9.5.4
version: kamailio 5.5.1 (x86_64/linux)

Once every few days the kamailio-proxy service stops working.

In addition, all calls that were in the crash receive incorrect values in
the duration field in the accounting.cdr table (the value from config.yml:
sems.sbc.calltimer_max is inserted). This translates into errors in the
settlement of costs / revenues from calls.

What can be done to avoid crash problems?

After analyzing the logs at the time of the problem, the following messages
appear:

Jun 26 12:50:48 spce proxy[1620965]: ALERT: <core> [main.c:788]:
handle_sigs(): child process 1639854 exited by a signal 11
Jun 26 12:50:48 spce proxy[1620965]: ALERT: <core> [main.c:791]:
handle_sigs(): core was generated
Jun 26 12:50:49 spce proxy[1620965]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
(0x7fba62313b08), called from core: core/usr_avp.c:
destroy_avp_list_unsafe(627), first free dialog: dlg_handlers.c:
dlg_iuid_sfree(332) - ignoring

Jul 12 14:58:19 spce proxy[2326544]: CRITICAL: <null> <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
(0x7fd3a413dd78), called from core: core/xavp.c: xavp_free_unsafe(100),
first free pv_headers: pvh_xavp.c: pvh_xavi_new_value(112) - ignoring
Jul 12 14:58:19 spce proxy[2326544]: CRITICAL: <null> <core>
[core/mem/q_malloc.c:123]: qm_debug_check_frag(): BUG: qm: fragm.
0x7fd3a46f9a90 (address 0x7fd3a46f9ac8) beginning overwritten (0)! Memory
allocator was called from core: core/xavp.c:100. Fragment marked by
(null):0. Exec from core/mem/q_malloc.c:511.
Jul 12 14:58:27 spce proxy[2326534]: ALERT: <core> [main.c:788]:
handle_sigs(): child process 2326544 exited by a signal 6
Jul 12 14:58:27 spce proxy[2326534]: ALERT: <core> [main.c:791]:
handle_sigs(): core was generated

Jul 13 14:47:42 spce proxy[2748943]: CRITICAL: <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
(0x7f42879e7728), called from core: core/xavp.c: xavp_free_unsafe(100),
first free core: core/xavp.c: xavp_free_unsafe(100) - ignoring
Jul 13 14:47:49 spce proxy[2748960]: CRITICAL: <core> [core/pass_fd.c:277]:
receive_fd(): EOF on 19
Jul 13 14:47:49 spce proxy[2748924]: ALERT: <core> [main.c:788]:
handle_sigs(): child process 2748943 exited by a signal 11
Jul 13 14:47:49 spce proxy[2748924]: ALERT: <core> [main.c:791]:
handle_sigs(): core was generated

Jul 21 09:28:22 spce proxy[1847220]: CRITICAL: <core> [core/pass_fd.c:277]:
receive_fd(): EOF on 15
Jul 21 09:28:22 spce proxy[1846976]: ALERT: <core> [main.c:788]:
handle_sigs(): child process 1847155 exited by a signal 11
Jul 21 09:28:22 spce proxy[1846976]: ALERT: <core> [main.c:791]:
handle_sigs(): core was generated

Jul 28 14:21:23 spce proxy[512865]: CRITICAL: <null> <core>
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
(0x7f109aa825f0), called from core: core/usr_avp.c:
destroy_avp_list_unsafe(627), first free dialog: dlg_handlers.c:
dlg_iuid_sfree(332) - ignoring
Jul 28 14:21:31 spce proxy[512882]: CRITICAL: <core> [core/pass_fd.c:277]:
receive_fd(): EOF on 20
Jul 28 14:21:31 spce proxy[512842]: ALERT: <core> [main.c:788]:
handle_sigs(): child process 512865 exited by a signal 11
Jul 28 14:21:31 spce proxy[512842]: ALERT: <core> [main.c:791]:
handle_sigs(): core was generated

Best Regards,
Rickey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230731/c60b8f83/attachment.html>