[c-nsp] Memory leak

[Rodney Dunn]

On Mon, Oct 17, 2005 at 07:11:37PM +0200, Javier Castillo Alcibar wrote:
> This process, "TCP Protocols" is increasing, over the time, its
> Allocated memory, but nerver frees memory.......How can I know which
> process is deallocating those blocks?

You can't.

> 
> I did some searchs in the bug toolkit, and I found some bugs related
> with memory leaks, but none of them seem to be related with my
> problem.....

You need to get the information I suggested to narrow it down.
Specifically the 'sh proc mem <PID>' over time.

> 
> BTW, the "Memory Leak Detector" feature, can help me in this case?

You could try it:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_feature_guide09186a008029cafe.html

Usually in the field we can figur it out just with the 'sh proc mem <PID>'
over time.

If you know it's TCP then try and focus on what TCP sessions 
are connecting and try to help narrow down the trigger. That will
help TAC verify if and what bug it is.

> 
> Javier.
> 
> 
>  
>  
>  
> 
> -----Mensaje original-----
> De: Rodney Dunn [mailto:rodunn at cisco.com] 
> Enviado el: lunes, 17 de octubre de 2005 19:00
> Para: Javier Castillo Alcibar
> CC: cisco-nsp at puck.nether.net
> Asunto: Re: [c-nsp] Memory leak
> 
> Just because a process allocates a block doesn't mean it is the only one
> that can free the same block.
> 
> Monitor 'sh proc mem' over time and if the free amount keeps decreasing
> them compare 'sh process memory' to find the one that is holding more
> and more memory.
> 
> Then monitor: sh proc mem <PID> for that process and open a TAC case for
> it so they can decode the functions for those PC's.
> 
> Rodney
> 
> On Mon, Oct 17, 2005 at 06:49:31PM +0200, Javier Castillo Alcibar wrote:
> > Hello list,
> >  
> > I have two routers, 2610 and a 2651XM, with the same IOS: the latest 
> > and wonderful 12.4(3a). Both routers have the same problem: they have 
> > a memory leak, and I guess that the guilty process is one called "TCP
> > Protocols":
> >  
> > router>show proc memory | include TCP Protocols
> >   98   0   31173056          0      15120          7          7 TCP
> > Protocols   
> > router>
> >  
> > Notice how big is the allocated memory number, 31173056, and how small
> 
> > is the freed memory number, 0 :)
> > 
> > Do you know what the hell is doing this process?? 
> >  
> > Thx a lot.
> > regards,
> > Javier.
> > 
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/