@miconda please look into this one. because now a days developer already
started to move for kamailio in lua. if there is memory leak then it will be
great issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thank you for the updates. :-)
--
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/1577#issuecomment-408659508___
Kamailio (SER) -
Didn't get the chance to look at it, being in a trip to USA (Cluecon). Hope to
get back to it soon, after returning.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda please let me know if this issue is reproduced by the same config at
your side or not
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda are you able to reproduce it?
--
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/1577#issuecomment-406842466___
Kamailio (SER) -
yes i am using master branch only.
--
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/1577#issuecomment-404770193___
Kamailio (SER) -
So, I assume it is still there in the master branch, after my last commit
realted to app_lua. I will try to reproduce here with the first available time
frame.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
this can be reporduced by following lua config
kamailio.cfg
```
#!KAMAILIO
### Defined Values #
#!substdef "!MY_IP_ADDR!!g"
#!substdef "!MY_EXTERNAL_IP!!g"
#!substdef "!MY_UDP_PORT!5060!g"
#!substdef "!MY_UDP_ADDR!udp:MY_IP_ADDR:MY_UDP_PORT!g"
# Dispatcher File
#!define
Updates:
I am running test with master branch. i will report if i found memory leak with
simple config so you can reproduce.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
An update -- I pushed a commit to restore the Lua execution stack. Try with
latest master and if the issue is still expose, try to give the minimal configs
and scripts to reproduce, as I wrote in my previous comment.
--
You are receiving this because you are subscribed to this thread.
Reply to
Did you run and test it long enough that the memory increased a lot? I checked
the logs for couple of PIDs and no relevant leak is reported.
Maybe you can make minimal kamailio.cfg and kemi lua script along with a sipp
scenario that I can use and reproduce here.
--
You are receiving this
[vg.log](https://github.com/kamailio/kamailio/files/2173037/vg.log)
Please check the valgrind log.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I do not see any new relevant information attached here, have you run with
valgrind as I metioned in my previous comment? It should give the report if
there are leaks for system memory.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
@miconda please see this issue.
--
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/1577#issuecomment-402530641___
Kamailio (SER) -
yeah sure i will run that one. i am using both ways
1. using lua modules
2. without using lua modules
both ways i can figure out that system memory getting increases.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Are you loading and using any Lua modules/libraries?
Or it is just using the KSR module exported by Kamailio? Are you issuing often
reloads of lua script?
The way to troubleshoot leak of system memory is to run kamailio via valgrind
(http://valgrind.org/). Do not forget you have to track
we are seeing the memory related system increasing to 97% so its might the case
that system memory getting increase.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It is not clear what type of memory leaks? Is it the on managed by kamailio in
pkg or shm? Or is the system memory? Because in the shell script you use
system's `free`.
To watch kamailio's shm memory do:
```
kamctl stats shmem
```
For pkg:
```
kamctl rpc pkg.stats
```
If it is system
more log for pkg_memory
```
1 ip-172-31-11-179 kamailio[11425]: ALERT: qm_status: alloc'd
from app_lua: app_lua_api.c: sr_lua_load_script(136)
1 ip-172-31-11-179 kamailio[11425]: ALERT: qm_status: alloc'd
from app_lua: app_lua_api.c: sr_lua_reload_script(451)
script to memory count for kamailio process
```
#!/bin/bash
free
echo ""
for line in $(pgrep -f '/usr/local/sbin/kamailio -f /etc/kamailio/kamailio.cfg
-P /var/run/kamailio.pid -m 16 -M 8 -u root -g root')
do
pms=$(pmap -x $line|grep total)
echo "$pms
@miconda rightnow our memory utilization are 97%.
--
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/1577#issuecomment-401450253___
### Description
We are using lua base routing with app_lua. We are seeing that our
memory-utilization on that system continuously getting increase. our route.lua
will have all routing logic same as
22 matches
Mail list logo
