I did a bit of digging in the source code. The patch which Dan mentioned
as fixing this bug exists in 10.10, so this bug is fixed.
JC, it sounds like you have a different bug happening. I am currently
unable to reproduce it using my 64-bit 10.10 system, but if you open a
new bug with the 'ubuntu-b
I am having a huge memory leak on my 64 bits system using either tcpdump or
dumpcap. Soon after the process is started, it starts eating all the memory is
swapping. In a few seconds, without much network traffic, I get 1 GB of memory
eaten.
So I think the bug is still here with Ubuntu 10.10, tho
Very sorry for taking so long to respond to this.
Since, as you pointed out, the fix appears to be upstream already, can
you please check to see if this bug still exists in the current
development release of Ubuntu, lucid lynx?
** Changed in: libpcap (Ubuntu)
Status: New => Confirmed
--
Now I've looked at the latest libpcap code from tcpdump.org: 'git clone
git://bpf.tcpdump.org/libpcap'.
The file pcap-usb-linux.c there already has this fixed! What goes?
--
Memory leak from libpcap on Karmic Koala
https://bugs.launchpad.net/bugs/476734
You received this bug notification because
