[SR-Users] [dispatcher] freeing already freed pointer, called from core: core/xavp.c: xavp_free

[Denys Pozniak]

Hello!

The configuration below leads to a CRITICAL message in the console.
Please let me know how to avoid this issue.

event_route[htable:mod-init] {
  route(AUTORUN);
...
}

route[AUTORUN]  {
  if ( ds_select("9", "4") ) {
    xlog("L_WARN", "[$cfg(route)] *ds_select* $xavp(_dsdst_[0]=>uri)
$xavp(_dsdst_[1]=>uri) $xavp(_dsdst_[2]=>uri)\n");
  }
...
}

dispatcher.list
# group 9
9 sip:192.168.20.125:5070
9 sip:192.168.20.160:5070
9 sip:192.168.20.7:5070
9 sip:192.168.20.107:5070
9 sip:192.168.20.190:5070

 0(6088) DEBUG: dispatcher [dispatch.c:2054]: ds_manage_routes(): set [9]
 0(6088) DEBUG: dispatcher [dispatch.c:2158]: ds_manage_routes(): using alg
[4] hash [0]
 0(6088) DEBUG: dispatcher [dispatch.c:2199]: ds_manage_routes(): selected
[4-9-2/0] <sip:192.168.20.190:5070>
 0(6088) DEBUG: dispatcher [dispatch.c:2218]: ds_manage_routes(): using
first entry [9/0]
 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/1]
 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/2]
 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/3]
 0(6088) DEBUG: dispatcher [dispatch.c:2272]: ds_manage_routes(): using
default entry [9/4]
 0(6088) DEBUG: dispatcher [dispatch.c:2016]: ds_select_dst_limit():
selected target destinations: 5
 0(6088) WARNING: <script>: [AUTORUN] *ds_select* sip:192.168.20.190:5070
sip:192.168.20.107:5070 sip:192.168.20.7:5070

 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list 0x7fe5f7d4f420
 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list (nil)
 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list (nil)
 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list (nil)
 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list (nil)
 1(6089) DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying
list (nil)
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list 0x7fe5f7d4faf0
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4faf0), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4f168), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4f378), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4f580), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4f790), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/xavp.c:495]: xavp_destroy_list(): destroying
xavp list (nil)
 1(6089) CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG:
freeing already freed pointer (0x7fe5f7d4f9a0), called from core:
core/xavp.c: xavp_free(65), first free core: core/xavp.c: xavp_free(65) -
ignoring
 1(6089) DEBUG: <core> [core/receive.c:457]: receive_msg(): cleaning up
...

version: kamailio 5.2.2 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX,
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024,
BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 19:29:40 Jun 20 2019 with gcc 4.8.5


-- 

BR,
Denys Pozniak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191217/23dd1d3d/attachment.html>