https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15777
Bug ID: 15777
Summary: `tshark -G folders`leaves mmdbresolve process behind
Product: Wireshark
Version: Git
Hardware: x86
OS: Mac OS X 10.4
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: ger...@wireshark.org
Target Milestone: ---
Build Information:
TShark (Wireshark) 3.1.0 (v3.1.0rc0-762-g9f875e98)
Copyright 1998-2019 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, with GLib 2.58.3,
with zlib 1.2.11, with SMI 0.5.0, with c-ares 1.15.0, with Lua 5.1.5, with
GnuTLS 3.6.6 and PKCS #11 support, with Gcrypt 1.8.4, with MIT Kerberos, with
MaxMind DB resolver, with nghttp2 1.36.0, with brotli, with LZ4, with Snappy,
with libxml2 2.9.4.
Running on Mac OS X 10.14.4, build 18E226 (Darwin 18.5.0), with Intel(R)
Core(TM) i9-8950HK CPU @ 2.90GHz (with SSE4.2), with 32768 MB of physical
memory, with locale en_US.UTF-8, with libpcap version 1.8.1 -- Apple version
79.250.1, with GnuTLS 3.6.6, with Gcrypt 1.8.4, with brotli 1.0.7, with zlib
1.2.11, binary plugins supported (0 loaded).
Built using clang 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.46.4).
--
If I run `tshark -G folders` on my development machine here I end up with an
orphan mmdbresolve process that consumes a CPU core. The process can be killed
with a TERM or HUP signal. The issue appears to be with GLib 2.58:
OS + Version WS Branch GLib Version Status
macOS 10.14.4 master 2.58.3 orphan
macOS 10.14.4 master-3.0 2.58.3 orphan
macOS 10.14.4 master 2.60.2 OK
macOS 10.14.4 master[1] 2.37.6 OK
Ubuntu 18.04 master 2.56.3 OK
[1] Installed from a recent macOS automated build.
--
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
