Home page logo

wireshark logo Wireshark mailing list archives

Re: Memory consumption in tshark
From: Jakub Zawadzki <darkjames-ws () darkjames pl>
Date: Wed, 28 Aug 2013 08:47:33 +0200

On Tue, Aug 27, 2013 at 06:17:13PM -0400, Evan Huus wrote:
As Anders says, this is because we have no way right now to selectively
discard it: much of the data is stored in a way that we can only get rid of
all of it, or none.

I'm not sure why we want to do selectvely discard, I'm fan of 'get rid of all of it'.

I'm sure there are some significant improvements we could make if somebody
figures out how, 

It's quite simple just call epan_free(), epan_new() after each packet
(or every N-th packet, or 
when dissection throw OutOfMemory exception - ups it could be too late ;])
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]