https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7833
--- Comment #11 from Bill Meier <wmeier@xxxxxxxxxxx> 2012-10-15 07:14:51 PDT ---
So: something about the traffic you are capturing is causing Wireshark to chew
up memory.
To be able to diagnose the issue, we'll need a capture file with that data.
Given that you note that you see Wireshark memory increasing "when starting a
new capture", it sounds like maybe just starting a capture with Wireshark,
letting it run for a short while, and then stopping the capture (before there's
a crash) will result in a file we can use for problem diagnosis.
As noted above you can mark this bug as private if you wish to restrict access
to any file attached to the bug to the Wireshark core developers.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
