[LEGO <luis.ontanon@xxxxxxxxx>]

Yes,
 although there are probably leaks, these should be a negligible part
of memory usage. ethereal is stateful. i.e. it keeps information while
dissecting, this is needed for things like packet reassembly (like for
tcp streams), conversations (like discovering what ports are to be
RTP) and other things.

You might want to pass through the preferences and disable
desegmentation, and reassembly functionality for some protocols to
save memory but that means that there on you might not be able to see
for example the body of an http request.


On 3/13/06, Alessandro Staltari <a_staltari@xxxxxxxx> wrote:
> I used tethereal to filter by date some packets saved
> in a file during a previous capture session (it was
> about 700MB of data collected in a week and I wanted
> to split them by day).
> While tethereal was running I saw the memory used by
> the program was increasing up to reaching an amount of
> memery comparable to the size of the input file.
>
> Is this behavoir normal?
>
> Thanks.
>
> Alessandro Staltari
>
>
>
>
>
>
>
> ___________________________________
> Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
> http://mail.yahoo.it
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>


--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan