[asterisk-dev] [Asterisk 16.x / pjsip TLS] Memory leak with core reload

[Michael Maier]

Hello Joshua!

Many thanks for your continuous effort supporting the community!

Unfortunately, I'm very busy currently and therefore I can't do the necessary investigations to narrow down the issue or just anonymise my asterisk config.

On Mon, Sep 30, 2019, at 17:48 Joshua C. Colp wrote:
> On Sat, Sep 28, 2019, at 11:31 AM, Michael Maier wrote:
>> On 28.09.19 at 12:32 Joshua C. Colp wrote:
>>> On Sat, Sep 28, 2019, at 6:20 AM, Michael Maier wrote:
>>>> Hello!
>>>>
>>>> While testing for a memory leak since pjsip 4.9 I detected, that there
>>>> seems to be another memory leak concerning core reload with pjsip and 4
>>>> TLS trunks / 2 endpoints.
>>>> Each core reload rises memory usage about ~ 2 MB (some times more (up
>>>> to 3 MB), sometimes less).
>>>> That's not a big deal for me as my configuration is mostly statically -
>>>> but for others having more endpoints / trunks and often change the
>>>> config this could be a serious
>>>> problem.
>>>
>>> Please file an issue[1] with a configuration that exhibits this (for example does your transport have allow_reload set to yes, as that would alter things).
>>
>> No - allow_reload is set to no.
> 
> I tried to reproduce this this morning and was unable to. I also asked Kevin to try to reproduce it who triaged the original memory leak issues and he was also unable to. Can you please file an issue like I mentioned with the specific configuration/scenario so we can see if something is up?

A few global words about my config at the moment:
- It's FreePBX 14 based
- There are 4 pjsip SIPS / SRTP trunks
- 2 pjsip SIP trunks
- 1 IAX2 device (for fax)
- several FreePBX features activated, like follow me, e.g.
- 15 outbound routes
- 7 inbound routes
- 3 custom contexts
- a small blacklist

I'm not sure if I'm really able to create a reliable anonymised config with justifiable expenditure.


I found one more problem regarding the configuration options, provided by FreePBX, which should be supported by asterisk.
I'm referring to the possibility, to add additional options not supported by FreePBX using special config files like
pjsip.registration_custom_post.conf or pjsip.aor_custom_post.conf and pjsip.endpoint_custom_post.conf or pjsip.transports_custom_post.conf.
The last two files are working pretty fine as expected, but the first two just don't work.

I'm configuring in pjsip.registration_custom_post.conf for example:

[extName](+)
key=value

Asterisk reads it (asterisk complains if it doesn't know the key), but asterisk doesn't apply the provided value for a known key - it's always the default value. That's 
strange, too.



Thanks
Michael