Wireshark-dev: Re: [Wireshark-dev] Memory usage
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Tue, 19 May 2009 19:30:30 +0200
Hi,

You can run valgrind to find memory leaks.
Have you read: http://wiki.wireshark.org/KnownBugs/OutOfMemory
It explains a lot.

Thanx,
Jaap

Marc Milgram wrote:

I am trying to use wireshark on a 344 MB tcp dump file.  There are
3220951 packets in this trace.  After reading in the dump, wireshark is
using 3.2GB.  I tried to do a search, but wireshark seemed to hang while
using 7.5GB memory.  I suppose I was impatient, but the memory usage
seems a bit excessive to me.

I am running this on Fedora-11 with 4GB RAM, 4 Xeon cores.

Is there a way to tell if wireshark is leaking, or otherwise
wasting memory?

Is there some way to help isolate what is causing the memory pressure?

Is there some way to work around this issue?

Thanks in advance,

Marc Milgram