Comment # 2
on bug 12231
from Guy Harris
In order to filter and print packets, TShark needs to dissect the packets, and
it builds various data structures to do so, and those data structures grow the
more packets are dissected, so, yes, TShark will use, over time, more memory as
it runs.
There might be ways to have TShark, when it's doing a one-pass dissection
(which I assume it is here, as there's no -2 flag), free up memory that's not
going to be needed for any packets received in the future, but that's would be
a lot of work (mainly the "figuring out what's not going to be needed for any
packets received in the future" part), so it probably won't be done any time
soon.
You are receiving this mail because:
- You are watching all bug changes.
