[c-nsp] Memory leak
Rodney Dunn
rodunn at cisco.com
Mon Oct 17 12:59:51 EDT 2005
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/
More information about the cisco-nsp
mailing list