Comment # 4
on bug 11002
from [email protected]
(In reply to Michal Labedzki from comment #1)
> Maybe some dissectors ate it. Could you check if the same issue can be
> reproduce when you load and close capture file from that live capturing? If
> so please share it. Or please provide information what interface you use
> (wlan0, eth0, bluetooth0?) and/or what protocols have you in capture.
I have reproduced this issue now (by sending a few million UDP packets out of
eth0 in some seconds). Closing directly the capturing file from the live
capture and restarting Wireshark, loading the capturing file and closing it
does both not free the memory (except for a few MiB).
I'm also noticing that restarting a live capture does not result in an
immediate fast increase of memory usage on sending packets so the emem theory
seems to be true here.
You are receiving this mail because:
- You are watching all bug changes.