Comment # 4
on bug 8158
from Anders Broman
The potential problem is well worth invetigating but one thing worth noting
is the way Wireshark uses memory. We have our own memory management functions
ep(epithermal) and se(season) type memory, the memory pool used for these
functions are growing in 10 Mb steps as needed but not released when the
capture file is closed to speed up loading of the next capture file. So memory
usage will not "return" to the initial value if a capture file is closed.
Regrads
Anders
You are receiving this mail because:
- You are watching all bug changes.