Closed #2027.
--
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/2027#event-2569140128___
Kamailio (SER) - Development Mailing List
Patches are backported to branch 5.2.
--
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/2027#issuecomment-522949345___
Kamailio (SER) -
Hi @miconda . I can confirm that this patch works. I put through ~ 4000 calls
and roughly a 100kb increase in memory across all children (25kb each), and
only as the first couple of calls came in. After that, 0 growth.
I believe this is fixed, thanks so much! I'll leave this open as you said
Whoops! Thanks Daniel, looks like I forgot to make install on my UAT server.
I'll re-test and update ASAP.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The version you used is before the fix -- the commit id in your version points
to:
```
commit 4c537a618949eb48ffed9297f3abc8cdc879b70d
Author: Daniel-Constantin Mierla
Date: Tue Aug 6 21:37:56 2019 +0200
misc_radius: increase MAX_EXTRA from 4 to 8
```
To have the version with the fix,
Hi @miconda. Thanks so much for this!
I tested with **kamailio 5.3.0-dev7 (x86_64/linux) 4c537a**
Unfortunately after ~ 20 hours/10k calls:
https://paste.ubuntu.com/p/vBmpQXKztj/
I somehow lost the dump I took initially, however please find attached graph
using the flawed methodology I used
Ah, this might be the cause that I did not managed to reproduce it with only
one module..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
This may have been a result of having two modules using the same callback to
update the content of the outbound buffer, in your case the topoh (hiding
header attributes) and dialog (updating the cseq).
I pushed a bunch of patches to core and modules using this callback. They are
in master
Update: app_ruby issues have been fixed in latest master. I'll build a new
machine on latest master tonight and split some live calls over there with
topoh enabled to see if we can replicate the issue in master. Will report back
in ~ 24 hours
--
You are receiving this because you are
### Description
I've noticed PKG memory increasing since enabling the topoh module last week in
a significant manner (~7MB per worker over 3000 calls split between 4 workers).
Removing the topoh module removed the memory usage.
Here is a pkg dump of one of the process post 3000 calls:
10 matches
Mail list logo
