Hi Roger,
The system monitor will only show you the amount of memory in use by
programs, not what your OS is using as cache as well. If you add the
system monitor to a taskbar, you can view both. I've seen it on my
machine as well, if a lot is being used by cache, and has to be page
file swapped out while a large capture is loading, wireshark will
sometimes crash. (see attached pic)
Regards,
Anthony
On 04/22/2010 03:19 PM, Wynns, Roger [OXFORD] wrote:
Gentlemen,
I
was trying to open a 200MB .pcap file into Wireshark(1.2.2)
under
Ubuntu(see
System Monitor.png) and I got the OutOfMemory message.
According
to the System Monitor, I was not out of memory(see
OutOfMemory.png).
I have read the Wiki page and it said that
it would use
all
available memory/swap space.
Is
there some setting that I need to set to force it to use all
memory
and/or
swap space?
Any
other reason that it is not using all the memory?
Thanks,
Roger
Wynns
Thanks,
Roger
Wynns
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
--
Anthony
Murabito
Operations Manager, R&D
WLAN
Consortium
UNH
InterOperability
Lab
+1.603.862.2263
|
Attachment:
Screenshot.png
Description: PNG image
