Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12231] New: tshark uses ever increasing amount of memory

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12231
Summary	tshark uses ever increasing amount of memory
Product	Wireshark
Version	unspecified
Hardware	x86
OS	All
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	TShark
Assignee	bugzilla-admin@wireshark.org
Reporter	matt@carterfamily.net.au

Build Information:
TShark (Wireshark) 2.0.1

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with libz 1.2.8, with GLib 2.46.2, without SMI, without c-ares, without ADNS,
with Lua 5.2, with GnuTLS 3.4.7, with Gcrypt 1.6.4, with MIT Kerberos, without
GeoIP.

Running on Linux 4.4.1-2-ARCH, with locale en_AU.UTF-8, with libpcap version
1.7.4, with libz 1.2.8, with GnuTLS 3.4.9, with Gcrypt 1.6.5.
Common KVM processor

Built using gcc 5.3.0.

--
I have observed that when tshark is left running it appears to use an ever
increasing amount of memory. For example

844 root      20   0 1621152 1.119g  10096 S  0.3 38.0   2:06.90 tshark -n
-s1600 -Y smtp


after restart

 2913 root      20   0  267328 134864  54640 S  0.0  4.4   0:05.76 tshark -n
-s1600 -Y smtp                                         

this results in tshark exhausting the memory on my VPS over a period of time

---

      You are receiving this mail because:

• You are watching all bug changes.