Apostolos Pantsiopoulos wrote:
I noticed while tweaking the module that there might be a memory leak problem. I monitored the freeswitch process using the simple top linux program and the sipp call generator. When the radius module is activated then FS starts consuming more memory in a linear manner. I used a 10 calls / sec rate with sipp (zero call length) and the memory reached 200 MB in just a few minutes.
if you let it run, does it keep using more and more memory? or does it top out somewhere?
At first I suspected my additions to the module to be the problem, but I found out that the same thing happened using the module in its current svn state (i.e. without my patch).
I followed the wiki's guidelines for creating a patch, but I don't know how the whole patch submitting "protocol" works. Should I create an account on jira? yes Should I post the patch here first until it is in an "acceptable" state? no Should I send the patch to a code maintainer and let him decide what to do? yes, through jira
-Ray