[BUG] Shared memory leak on using $shv

[ankogan]

OpenSIPS version you are running

version: opensips 3.6.4 (x86_64/linux)
flags: STATS: On, SHM_EXTRA_STATS, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, F_PARALLEL_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 4096, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: 2367deb8e
main.c compiled on  with gcc 8

Describe the bug
There is a memory leak on using $shv in such a case:

$var(sdp) = $(var(sdp){re.subst,/^s=.*/s=$shv(voip_sdp_session)\r/});
...
add_body_part("$var(sdp)", "application/sdp");

There is no leaks in case

$var(voip_sdp_session) = $shv(voip_sdp_session);
$var(sdp) = $(var(sdp){re.subst,/^s=.*/s=$var(voip_sdp_session)\r/});
...
add_body_part("$var(sdp)", "application/sdp");

OS/environment information

• Operating System: Debian 10, 12
• OpenSIPS installation: manual packages

[github-actions]

Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.

[bogdan-iancu]

Hi @ankogan , could you run several (hundreds or thousands) such subst (the leaking ones) and provide a shm memory dump? See https://opensips.org/Documentation/TroubleShooting-OutOfMem on how to generate a runtime mem dump.

[bogdan-iancu]

BTW, I assume the $var(sdp) is an SDP (the original one) and the $shv(voip_sdp_session) var holds some session name, right ?

[bogdan-iancu]

Also upgrade to the latest 3.6 minor, the 3.6.6 to be sure you have all the fixes https://www.opensips.org/About/Version-3-6-x

[ankogan]

Hi Bogdan,
$var(sdp) is the result of rtpengine_offer(), $shv(voip_sdp_session) - session name. I use shared vars as global parameters.
Will check with 3.6.6.

[bogdan-iancu]

@ankogan , also check this https://opensips.org/Documentation/TroubleShooting-OutOfMem - and try to get a shared-mem dump, showing the leak you suspect.
I reviewed the code and found nothing to indicate a leak.