6 Aug
2019
6 Aug
'19
4:01 p.m.
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please
use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on
sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask
on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the
developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### 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:
https://paste.ubuntu.com/p/85KYg7gD2z/
### Additional Information
```kamailio 5.3.0-dev4 (x86_64/linux) 6d43ea-dirty. ```
I'm unsure why it's tagged dirty, as I simply cloned master and reset to
6d43eacd6d5b78fe857267e70b7fa85519a7d5b6.
I do plan to test this on dev7, however an unrelated issue is preventing me from testing
this with my app_ruby based code.
--
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