Hi, John!
I think you might spot something. Can you apply this patch[1] and try again?
[1] https://gist.github.com/razvancrainea/03a43bfa8b554a7ca89f2740a3c54c96
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 03/10/2017 10:02 AM, John Nash wrote:
Dear Razvan,
I think I found one issue in do_routing function if i
pass gw_whitelist then only i see this drop of memory. If I skip this
parameter private memory does not increase with every call.
Regards
Manoj
On Thu, Mar 9, 2017 at 7:29 PM, John Nash <[email protected]
<mailto:[email protected]>> wrote:
If I use 2.2 will it give clearer picture of memory allocation? or 2.3
On Thu, Mar 9, 2017 at 7:21 PM, Răzvan Crainea
<[email protected] <mailto:[email protected]>> wrote:
There's no need for that. No function should leak in any
circumstances :)
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>
On 03/09/2017 03:27 PM, John Nash wrote:
OK..May i send you my script privately?
On Thu, Mar 9, 2017 at 6:13 PM, Răzvan Crainea
<[email protected] <mailto:[email protected]>> wrote:
Hi, John!
No, I nothing is suspicious. Definitely not from the
drouting module.
Try to make two captures: one after 10 calls, another one
after 20 calls.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
<http://www.opensips-solutions.com>
On 03/09/2017 01:50 PM, John Nash wrote:
Do you see anything suspicious in the latest mem dump?
On Wed, Mar 8, 2017 at 7:20 PM, John Nash
<[email protected] <mailto:[email protected]>>
wrote:
One more useful info. I disabled drouting functions
and just rewrote RURI to hardcoded address keeping
rest of the functions same and I do not see drop in
private memory of that process.
On Wed, Mar 8, 2017 at 4:40 PM, John Nash
<[email protected]
<mailto:[email protected]>> wrote:
OK Here is the dump
https://drive.google.com/open?id=0BxJKNwFalcRMX0xDUlRIa2VUdG8
<https://drive.google.com/open?id=0BxJKNwFalcRMX0xDUlRIa2VUdG8>
I increased syslog message rate to 500000, Made
around 10 call attempts. Waited for some time
and made sure no call is on server and then sent
signal to dump memory to the process ID i suspect.
On Wed, Mar 8, 2017 at 4:07 PM, Răzvan Crainea
<[email protected]
<mailto:[email protected]>> wrote:
No, you should not kill any process. Simply
send a SIGUSR1 to the process you suspect.
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
<http://www.opensips-solutions.com>
On 03/08/2017 12:28 PM, John Nash wrote:
Sorry...Should I kill only the process
where i see memory leak?
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
