Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 4711] After running a trace overnight Wireshark stops responding

Wireshark-bugs: [Wireshark-bugs] [Bug 4711] After running a trace overnight Wireshark stops resp

Date: Wed, 28 Apr 2010 05:52:50 -0700 (PDT)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4711

--- Comment #2 from bigmags@xxxxxxxxx 2010-04-28 05:52:48 PDT ---
(In reply to comment #1)
> For long running captures, use the capture engine only. Avoid Wireshark
> dissecting and collecting state for such a long time, eventually causing it to
> run out of memory.
> Look into running dumpcap on the command line.

Thanks Jaap. 

This worked well and thanks for the help and insight.

Martin

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

References:
- [Wireshark-bugs] [Bug 4711] New: After running a trace overnight Wireshark stops responding
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 4719] build failure: undefined reference to `manual_addr_resolv_dlg'
Next by Date: [Wireshark-bugs] [Bug 4719] build failure: undefined reference to `manual_addr_resolv_dlg'
Previous by thread: [Wireshark-bugs] [Bug 4711] After running a trace overnight Wireshark stops responding
Next by thread: [Wireshark-bugs] [Bug 4712] New: Dissection of BSSMAP IEs: Old BSS to New BSS Info and New BSS to Old BSS Info
Index(es):
- Date
- Thread