https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5184
--- Comment #3 from PlayerPL <twieczorkowski@xxxxxxx> 2010-09-06 06:29:22 PDT ---
(In reply to comment #2)
> > If there is a problem with the memory, maybe just try to save some packets "in flight" on hard drive instead of memory ?
> That's exactly what we do and have always done.
> However, other things consume a significant mount of memory, including packet
> reassembly and - to a lesser degree in 1.4 - column contents for the packet
> display. See the link that Anders gave.
OK. So maybe the additional solution like :
________________________-----------------------------______________
Old data saved to disk Data visible in wireshark New incoming data
The Wireshark will be consume only some amount of memory for current data.
Data of oldest captured packets (like above visible 500000 of packets) will ba
saved on disk, and visible only when you open this data from the saved file.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
