[Devel] Mem-leak in tm-module?

[Bogdan-Andrei Iancu]

Hi Sumeet,

the preliminary tests on Andreas side shows that the last fixup solved 
the problem. So either you do no use the latest CVS, either is a 
different story. If so, please see the wiki for how to analyse and 
eventualy ebug memory problems:
http://openser.org/dokuwiki/doku.php?id=memory

the important think is first to figure out if it's a temporary memory 
outage or if it is a leak leading to mem starvation. Please go through 
the doc.

regards,
bogdan


Sumeet Gupta wrote:

> Hi Bogdan,
>
> It doesnt seem to have fixed the memory problem. Actually this memory 
> error also occured in the previous version I was running of "openser 
> 1.1.0-dev17-notls". Also note the next_gw lcr error.
>
>
> Jun 26 17:50:11 sipserver01 /sbin/openser[15337]: ERROR: new_t: out of 
> mem:
> Jun 26 17:50:11 sipserver01 /sbin/openser[15337]: ERROR: t_newtran: 
> new_t failed
> Jun 26 17:50:14 sipserver01 /sbin/openser[15337]: ERROR: 
> sip_msg_cloner: cannot allocate memory
> Jun 26 17:50:14 sipserver01 /sbin/openser[15337]: ERROR: new_t: out of 
> mem:
> Jun 26 17:50:14 sipserver01 /sbin/openser[15337]: ERROR: t_newtran: 
> new_t failed
> Jun 26 17:50:18 sipserver01 /sbin/openser[15353]: ERROR: 
> append_branch: max nr of branches exceeded
> Jun 26 17:50:18 sipserver01 /sbin/openser[15353]: next_gw(): ERROR: 
> do_action failed with return value <-1>
> Jun 26 17:50:22 sipserver01 /sbin/openser[15353]: ERROR: 
> append_branch: max nr of branches exceeded
> Jun 26 17:50:22 sipserver01 /sbin/openser[15353]: next_gw(): ERROR: 
> do_action failed with return value <-1>
>
>
>
>> From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
>> To: Sumeet Gupta <skg1010 at hotmail.com>
>> CC: andreas.granig at inode.info, devel at openser.org
>> Subject: Re: [Devel] Mem-leak in tm-module?
>> Date: Mon, 26 Jun 2006 23:27:16 +0300
>>
>> Hi Sumeet,
>>
>> have you tried to use the latest CVS head? I made a small fix couple 
>> of hours ago...please update and see if the problem persists.
>>
>> regards,
>> bogdan
>>
>> Sumeet Gupta wrote:
>>
>>> I believe I am experiencing the same problem. Increasing the shared 
>>> memory size does not help either. I increased it to 128 megs with 
>>> high load and still only moments after startup i recieve the 
>>> following errors.
>>>
>>> -Sumeet
>>>
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: 
>>> sip_msg_cloner: cannot allocate memory
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: new_t: out 
>>> of mem:
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: t_newtran: 
>>> new_t failed
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: 
>>> sip_msg_cloner: cannot allocate memory
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: new_t: out 
>>> of mem:
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: t_newtran: 
>>> new_t failed
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: 
>>> sip_msg_cloner: cannot allocate memory
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: new_t: out 
>>> of mem:
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21678]: ERROR: t_newtran: 
>>> new_t failed
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: 
>>> sip_msg_cloner: cannot allocate memory
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: new_t: out 
>>> of mem:
>>> Jun 26 11:44:58 sipserver01 /sbin/openser[21682]: ERROR: t_newtran: 
>>> new_t failed
>>> Jun 26 11:44:59 sipserver01 /sbin/openser[21680]: ERROR: 
>>> sip_msg_cloner: cannot allocate memory
>>> Jun 26 11:44:59 sipserver01 /sbin/openser[21680]: ERROR: new_t: out 
>>> of mem:
>>>
>>>
>>>> From: Andreas Granig <andreas.granig at inode.info>
>>>> To: devel <devel at openser.org>
>>>> Subject: [Devel] Mem-leak in tm-module?
>>>> Date: Mon, 26 Jun 2006 14:39:35 +0200
>>>>
>>>> Hi,
>>>>
>>>> Seems like there's another mem-leak in OpenSER (CVS HEAD). If I 
>>>> simulate thousands of calls, the proxy runs out of shared memory, 
>>>> with memlog-lines like the following at shutdown:
>>>>
>>>> 57583. N address=0xb77a87c0 frag=0xb77a87a8 size=888 used=1
>>>> alloc'd from mem/shm_mem.c: sh_realloc(86)
>>>> start check=f0f0f0f0, end check= c0c0c0c0, abcdefed
>>>>
>>>> sh_realloc is only called by shm_resize, which is only called in 
>>>> modules/tm/t_reply.c. Could somebody please check this?
>>>>
>>>> Thanks,
>>>> Andy
>>>>
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at openser.org
>>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>
>>>
>>>
>>> _________________________________________________________________
>>> Is your PC infected? Get a FREE online computer virus scan from 
>>> McAfee® Security. 
>>> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>
>>
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search! 
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>