Wireshark-bugs: [Wireshark-bugs] [Bug 5670] tshark leaks 100% memory
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 9 Feb 2011 06:26:11 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5670

Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jeff.morriss.ws@xxxxxxxxx
         Resolution|                            |INVALID

--- Comment #1 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2011-02-09 06:26:10 PST ---
*Using* memory is not the same as *leaking* memory.

Wireshark/tshark are not designed for long term captures, they are designed for
in-depth analysis.  You might want to look at using dumpcap to capture traffic
if you're going to be doing long captures (where memory usage can be a
problem).

Also, see: http://wiki.wireshark.org/KnownBugs/OutOfMemory

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