https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15229
Bug ID: 15229
Summary: Tshark memory leak
Product: Wireshark
Version: 2.6.4
Hardware: x86-64
OS: Red Hat
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: TShark
Assignee: bugzilla-ad...@wireshark.org
Reporter: sergiy.dr...@gmail.com
Target Milestone: ---
Created attachment 16668
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16668&action=edit
3 hour memory consumption graph
Build Information:
TShark (Wireshark) 2.6.4 (v2.6.4)
Copyright 1998-2018 Gerald Combs <ger...@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, without POSIX capabilities, without libnl, with
GLib 2.54.2, with zlib 1.2.7, without SMI, with c-ares 1.10.0, without Lua,
without GnuTLS, with Gcrypt 1.5.3, without Kerberos, without MaxMind DB
resolver, with nghttp2 1.31.1, with LZ4, with Snappy, with libxml2 2.9.1.
Running on Linux 3.10.0-862.14.4.el7.x86_64, with Intel(R) Xeon(R) CPU
E7450 @ 2.40GHz, with 3781 MB of physical memory, with locale en_US.UTF-8,
with
libpcap version 1.5.3, with Gcrypt 1.5.3, with zlib 1.2.7, binary plugins
supported (0 loaded).
Built using gcc 4.8.5 20150623 (Red Hat 4.8.5-28).
--
Dear Support Team!
It looks life tshark memory leak has been detected. Please help to localize and
solve the problem.
Tshark behaviour is reproducable with the next test conditions:
1) Red Hat Enterprise Linux Server release 7.5 (Maipo)
Linux 3.10.0-862.14.4.el7.x86_64
2) Traffic flow ~3.19 Mbps, ~1293.61 pps
3) Tshark prints captured packets to stdout which is piped to stdin of another
program.
tshark -q -ni lo -s 0 -f 'ether host xx:xx:xx:xx:xx:xx or ether host
xx:xx:xx:xx:xx:xx or ether host xx:xx:xx:xx:xx:xx or ether host
xx:xx:xx:xx:xx:xx' -Y '((gsm_old.localValue == 2 || gsm_old.localValue == 3 ||
gsm_old.localValue == 7 || gsm_map.old.Component == 2) && ((sccp.called.digits
> 380999999999 || sccp.called.digits < 380000000000) || (sccp.calling.digits >
380999999999 || sccp.calling.digits < 380000000000)))' -V -T pdml | <another
program>
At the end tshark consumed all RAM and SWAP and OOM killer killed tshark &
dumpcap then.
In the attachment you can find 3 hour CPU and memory consumption graphs.
Best regards,
Sergiy Dryga.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
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
