["Guy Harris" <gharris@xxxxxxxxx>]

Ronnie Sahlberg said:
> Drawback would very likely be that memory usage would be significantly
> elevated but this might be a price worth paying
> to speed up re-filtering of captures. (Many users load a capture once and
> then filter that capture dozens of times)
> This behaviour could be made controllable from preferences and the default
> would be "optimize for memory usage (current model)"
> or "optimize for speed".

Given my experience when we had a memory leak, in the early days of the
protocol tree code, that caused protocol trees not to be freed, if we do
that, we'd definitely want to make it optional - when it had that leak,
Ethereal thrashed pretty badly when loading a large capture file.