Comment # 3
on bug 8158
from Mauro Pellizzer
-Yes each resizing gain about 10 MB of memory
-I am using it in a remote desktop windows, so I does not know if this change
something, but I neither resize wireshark or the remote windows, they are alway
maximized. (and I does not capture on the same interface used by remote
desktop)
-I have noticed that this happen only with the 32 bit version:
For example, in the 32 bit version (remote machine, 1.8.4) after 76 packets
(capture enclosed) the memory consuption is 322MB. If I restart the capture
each new packet Wireshark memory grow about 2MB/packet. Save, close and open
the file without close Wireshark memory grow about 15MB. If I start a new
capture is always 2MB/packet. Same test done by my colleague that have an XP
machine (no remote desktop). Same test done on the remote desktop interface
because the other traffic is mainly ospf, so it is not the ospf dissector.
In the 64 bit version (local machine, 1.8.4) after ~7000 packets (and a
"restart capture") the memory consuption is 96MB (the same traffic on the other
side, the 32 bit machine consume about 1GB of memory). After the restart
capture the memory does not grow for a long time. Save, close and open the file
without close Wireshark gain a bit of memory (KB). After a new capture is
started the memory does not grow until the packet number does not reach the
previous.
Thank you,
Mauro
You are receiving this mail because:
- You are watching all bug changes.