Wireshark-dev: Re: [Wireshark-dev] Wireshark Memory alloc question

From: rmkml <rmkml@xxxxxxx>
Date: Fri, 4 Apr 2008 05:45:00 +0200 (CEST)

Thanx Jaap,
maybe, for tshark and live trafic, you freeing mem after closed state session ?
Regards
Rmkml

On Fri, 4 Apr 2008, Jaap Keuter wrote:

Date: Fri, 04 Apr 2008 13:18:19 +0200
From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Reply-To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Wireshark Memory alloc question

Hi,

Yes, good idea. Can you tell us *when* we can free memory?

Thanx,
Jaap

rmkml wrote:

Hi,
On README.malloc file, wireshark have two functions:
-Ephemeral allocations: This functions allocate memory that will be automatically freed once the current packet dissection completes.
-Seasonal allocations: This functions allocate memory that will stay around a lot longer but will be automatically freed once the current capture is closed and Wireshark opens a new capture.

Very good, this two functions work very well on open/close pcap file,
but when wireshark/tshark run on live trafic (pcap_open_live), *shark more alloc without freeing.

Maybe it is possible add new function or modify *shark code for malloc freeing on live analysis ?

Regards
Rmkml
Crusoe-Researches.com

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev