https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14029
Bug ID: 14029
Summary: trustd and socketfilterfw high CPU usage when using
wireshark >= 2.4.0
Product: Wireshark
Version: 2.4.0
Hardware: x86-64
OS: macOS 10.12
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Qt UI
Assignee: bugzilla-ad...@wireshark.org
Reporter: ilario...@twilio.com
Target Milestone: ---
Created attachment 15813
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15813&action=edit
macOS firewall settings
Build Information:
Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
GLib 2.36.0, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with GeoIP,
with nghttp2 1.14.0, with LZ4, with Snappy, with libxml2 2.9.4, with
QtMultimedia, without AirPcap, with SBC, without SpanDSP.
Running on Mac OS X 10.12.6, build 16G29 (Darwin 16.7.0), with Intel(R)
Core(TM)
i7-5557U CPU @ 3.10GHz (with SSE4.2), with 16384 MB of physical memory, with
locale en_US.UTF-8, with libpcap version 1.8.1 -- Apple version 67.60.1, with
GnuTLS 3.4.17, with Gcrypt 1.7.7, with zlib 1.2.8.
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Since the update to 2.4.0 (also affects 2.4.1) I can't use Wireshark because
following processes start to use a lot of CPU right after Wireshark startup:
* trustd
* socketfilterfw
Version 2.2.9 works without any issues.
Note: I install Wireshark.app only without org.wireshark.ChmodBPF.plist and
command line utilities since I only use it to read PCAP files.
Attaching macOS firewall settings screenshot since it looks related.
--
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
