Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2000 18:48:03 +1000 (EST)
From:      Rowan Crowe <rowan@sensation.net.au>
To:        freebsd-isp@freebsd.org
Subject:   tcpdump - memory leak?
Message-ID:  <Pine.BSF.4.21.0005121622110.38247-100000@velvet.sensation.net.au>

next in thread | raw e-mail | index | archive | help
Hi all,

Any ideas on why the memory that tcpdump uses seems to rise over time? A
memory leak perhaps? I have a process that tracks link utilisation
and sends real time data to another host for graphing, and it uses
tcpdump for this. Here's what 'top' shows:

Mem: 11M Active, 1628K Inact, 5136K Wired, 536K Cache, 2516K Buf, 4544K Free
...
 6991 root     28   0  2904K  2820K RUN    104:29  0.04%  0.04% tcpdump

And after I kill and restart it:

Mem: 6068K Active, 1628K Inact, 5064K Wired, 536K Cache, 2544K Buf, 9584K Free
...
17609 root      4   0   900K   720K bpf      0:00  0.42%  0.27% tcpdump

Approximately 2 hours later, not sure if it's "rising" or just happens to
be using a bit more memory at this instant:

17609 root      4   0   984K   900K bpf      0:22  0.00%  0.00% tcpdump

The machine it runs on has an MFS file system with no swap, and it
occasionally reboots for no reason with no apparent ill after effects. I
am guessing it's because it runs out of available memory, and I think I've
just discovered why...

Any ideas appreciated.

Cheers.


--
Rowan Crowe                              http://www.rowan.sensation.net.au/
Sensation Internet Services                   http://info.sensation.net.au/
Melbourne, Australia                                 Phone: +61-3-9388-9260





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0005121622110.38247-100000>