Module: kamailio
Branch: master
Commit: fc358c8dabc227e86e4299d54ef6d3d29a46b096
URL:
https://github.com/kamailio/kamailio/commit/fc358c8dabc227e86e4299d54ef6d3d29a46b096
Author: Juha Heinanen
Committer: Juha Heinanen
Date: 2017-02-16T10:25:30+02:00
lib/srdb1: increased size of dialplan table
Module: kamailio
Branch: 5.0
Commit: 5a9716f9f4426375b0f99f499ade4d1785e0b600
URL:
https://github.com/kamailio/kamailio/commit/5a9716f9f4426375b0f99f499ade4d1785e0b600
Author: Juha Heinanen
Committer: Juha Heinanen
Date: 2017-02-16T10:28:45+02:00
lib/srdb1: increased size of dialplan table rep
Daniel-Constantin Mierla writes:
> I am fine to increase the size. The version number should not be
> increased, it is not a change that breaks any query and c code should
> have checks/or allocations based on the size. Should be also ok to
> backport.
OK, done, Juha
I think this will be fixed by edb9df8
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/872#issuecomment-280308975___
sr-dev mailing list
I've detected that the allocated shared memory is always growing due to
```
proxy[2527]: NOTICE: fm_status: count=376594 size= 103410648 bytes from
usrloc: ucontact.c: new_ucontact(98)
proxy[2527]: NOTICE: fm_status: count=1882939 size= 110079752 bytes from
usrloc: ../../ut.h: shm_str_dup(723)
I would say the origin of the problem is calls to get_urecord() without
release_urecord()
```
/*!
* \brief Release urecord previously obtained through get_urecord
* \warning Failing to calls this function after get_urecord will
* result in a memory leak when the DB_ONLY mode is used. When
* th
added some debug
notice in this example that ``ucontact[0x7f7b315f1d08]`` is never freed
REGISTER
```
Feb 16 17:04:43 sp1 proxy[9687]: NOTICE: