| Bug ID |
12258
|
| Summary |
Wireshark CPU usage has dramatically increased
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
Mac OS X 10.10
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.1.0-2322-g3c143d2 (v2.1.0rc0-2322-g3c143d2 from unknown)
Copyright 1998-2016 Gerald Combs <[email protected]> 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 Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.
Running on Mac OS X 10.10.5, build 14F1605 (Darwin 14.5.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Wireshark from current master is using dramatically more CPU than earlier
versions. The top utility is reporting that Wireshark is consuming 85% to 90%
of a CPU when it is simply at the welcome screen or with a small trace file
open. Normally top reports Wireshark CPU usage as less than 2%
I built own OS X version from master head and confirmed same problem. I used
git bisect to find the problem commit. The command "git bisect start 3c143d2
070fc33" process ultimately reported:
> # first bad commit: [28bfb3210537ce60895e10526f0a3e8cdfbd279d] Qt: Defer proto tree column content resizing.
I first noticed this issue yesterday after I updated a Macbook to use buildbot
Version 2.1.0-2322-g3c143d2. This system was previously using buildbot Version
2.1.0-2133-g070fc33.
With Wireshark Version 2.1.0-2322-g3c143d2 up and capturing with update packets
in real time enabled from a relatively low volume network (this network had an
average of less than 3 packets per second), the actual packets displayed were
several minutes behind the current wall clock time. This happened after less
than an hour of capturing. After stopping the capture it took several minutes
for the Wireshark GUI to catch up to the dumpcap captured packets.
I noticed that the MacBook's fan was running implying the CPU was busy. I
opened up the top utility and saw that Wireshark was using much more CPU than
expected even though Wireshark was now simply displaying a trace file. I
reinstalled the earlier buildbot Version 2.1.0-2133-g070fc3 and no longer saw
the excessive CPU utilization even when I started another hour long trace.
With this earlier version the Wireshark GUI effectively remained sychronized
with dumpcap.
You are receiving this mail because:
- You are watching all bug changes.