[Wireshark-bugs] [Bug 15229] Tshark memory leak (continuous live capture)

2018-12-15 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15229

Michael Mann  changed:

   What|Removed |Added

 CC||mman...@netscape.net
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Michael Mann  ---
(In reply to Peter Wu from comment #2)
> Hi Sergiy,
> 
> Unfortunately this is not a memory leak but a limitation of the current
> dissection engine. Dissection of a single packet can result in retaining
> persistent conversation information until the packet capture file is closed.

One suggestion would be to use the -b option as highlighted here:
https://blog.wireshark.org/2014/07/to-infinity-and-beyond-capturing-forever-with-tshark/

Closing as WONTFIX because as Peter noted, memory can be accumulated through
retained conversation information from packets and at least with the -b option
you can "reset" some of that accumulated memory.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15229] Tshark memory leak (continuous live capture)

2018-10-31 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15229

Peter Wu  changed:

   What|Removed |Added

Summary|Tshark memory leak  |Tshark memory leak
   ||(continuous live capture)
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||pe...@lekensteyn.nl

--- Comment #2 from Peter Wu  ---
Hi Sergiy,

Unfortunately this is not a memory leak but a limitation of the current
dissection engine. Dissection of a single packet can result in retaining
persistent conversation information until the packet capture file is closed.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe