[OpenSIPS-Users] Possible Memory Problem

Liviu Chircu liviu at opensips.org
Wed Mar 1 12:47:02 EST 2017


Thanks for the awesome report, Jim - I managed to pinpoint the issue 
immediately.

For now, you can actually prevent the leak by doing:

rest_get("https://www.opensips.org", "$var(body)", "$var(ctype)");

instead of:

rest_get("https://www.opensips.org", "$var(body)");

Nevertheless, a fix will be available soon.

Cheers,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 01.03.2017 18:39, Liviu Chircu wrote:
>
> It's:
>
> <bytes total>: <no_of_individual_allocations> x [ file: function, line ]
>
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com
> On 01.03.2017 18:10, Jim DeVito wrote:
>> Hi Liviu!
>>
>> Server:: OpenSIPS (2.2.3 (x86_64/linux))
>>
>> For my own understanding what does the numbers on either side of the 
>> colon mean? sip-proxy02 opensips: 364912 : 6634 x [rest_cb.c: 
>> header_func, line 88] I assume consumed memory vs released or 
>> something like that?
>>
>> Thanks for looking into this.
>>
>>
>> On Wed, Mar 1, 2017 at 10:58 AM, Liviu Chircu <liviu at opensips.org 
>> <mailto:liviu at opensips.org>> wrote:
>>
>>     Hi, Jim!
>>
>>     Catching memory leaks in OpenSIPS 2.2+ has never been more fun :)
>>     This definitely looks broken:
>>
>>     Mar  1 15:02:00 sip-proxy02 opensips: 364912 : 6634 x [rest_cb.c:
>>     header_func, line 88]
>>
>>     May I ask what version are you using? ("opensips -V") That's the
>>     first step in trying to reproduce this!
>>
>>     Regards,
>>
>>     Liviu Chircu
>>     OpenSIPS Developer
>>     http://www.opensips-solutions.com <http://www.opensips-solutions.com>
>>
>>     On 01.03.2017 17:28, Jim DeVito wrote:
>>>     Hi All,
>>>     Please take a look at my possible memory problem. The first part
>>>     of the pastebin is what I see in my log file when I do...
>>>     rest_get("http://localhost/cnam/?number=$avp(dipnum)
>>>     <http://localhost/cnam/?number=$avp%28dipnum%29>", "$avp(cnam)");
>>>     The second part is the memory dump from the running process with
>>>     the debugging flags compiled in.
>>>     http://pastebin.com/45QrtFts
>>>     Thoughts?
>>>     Thanks!!
>>>     P.S. Here is the original conversation.
>>>     https://opensips.org/pipermail/users/2016-November/035860.html
>>>     <https://opensips.org/pipermail/users/2016-November/035860.html>
>>>     -------------
>>>     Jim DeVito
>>>
>>>     _______________________________________________
>>>     Users mailing list
>>>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>     _______________________________________________ Users mailing
>>     list Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/users> 
>>
>> -- 
>> -------------
>> Jim DeVito
>> Mobile 216.507.9497
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170301/784ef9da/attachment.html>


More information about the Users mailing list