https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2573
--- Comment #4 from Sake <sake@xxxxxxxxxx> 2008-10-26 10:32:07 PDT ---
Since wireshark keeps state information about conversations even accross files
when capturing to multiple files, your memory footprint will indeed increase up
to the point that it just runs out of memory.
If you want to capture for long periods of time (more than 100 hours in your
case), it's better to use dumpcap which does not keep any state information. It
just writes network data to disk.
Could you give dumpcap a try and see if that solves your problem?
PS Of course improving the way wireshark behaves when it crashes would be nice
too, that just takes a lot of time which most of us unfortunately do not have
:(
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
