Hello,

can you try with the patch from this commit:

  - https://github.com/kamailio/kamailio/commit/e0f95ea7fc691f976564b07436848673c633195d

The memset() is optional, more for long term safety, the if block at the end of the function is relevant.

In 4.4, the file to change is modules/drouting/dr_time.c instead of src/modules/drouting/dr_time.c.

If all is fine, then I will backport it.

Cheers,
Daniel

Hi,

I have some kind of memory growth (leak?).

kamailio 4.4.1.

started with 64M for shmem, had a crash after 5 days of traffic.

increased shmem to 128, but still memory grows everyday.

when traffic load decrease, the memory growth stops but memory stays on the same level. when traffic increase again,used memory continue to grows again.

I started kamailio now with the "-x qm" option to debug shmem.

every half hour i dump the status of it.

there are several modules that the memory size is increasing (some of them are obvious).

but, one is very strange.... DROUTING

I am using drouting module for each call on my kamailio.

the DB tables are very small, and there is no reloads.

only one time used in my script :

..

...

subst_user('/(.*)/$avp(xxx)/');

if(!do_routing("$avp(yyyy)")){

 xlog...somthing;

return(-1)

}

..

....

the shmem that is rapidly growing and does not make sense is:

"from drouting: dr_time.c: ac_get_maxval(219)"

seems that when i used mem_join =1, the growth was smaller, but still significant.

now i use mem_join = 0, it seems rapidly increasing...

I have more information from the logs, will send it if necessary (it is just a lot...)

any ideas ?

cheers,

Uri

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com