Wireshark-bugs: [Wireshark-bugs] [Bug 11035] New: High CPU on Wireshark 1.99.3 running on OS X 1
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 07 Mar 2015 16:26:37 +0000
Bug ID 11035
Summary High CPU on Wireshark 1.99.3 running on OS X 10.10.2
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86-64
OS Mac OS X 10.10
Status UNCONFIRMED
Severity Critical
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter cjones@autonomic.ca 

Created attachment 13491 [details]
Process Sample of Wireshark 1.99.3 running on OS X 10.10.2

Build Information:
Version 1.99.3 (v1.99.3-0-g4f2c827 from master)

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 Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.3, 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,
without PortAudio, with AirPcap.

Running on Mac OS X 10.10.2, build 14C109 (Darwin 14.1.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, without AirPcap.
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
Removed existing .wireshark configuration folder from my home folder and
installed Wireshark 1.99.3 so I could run the development version with a clean
slate. Launched Wireshark and made some minor changes to the Wireshark
configuration (layout, colours, font, etc). Was able to run a few packet
captures but now everytime I load Wireshark 1.99.3 the CPU gets pinned 97% +.

I sampled the Wireshark process in OS X and attached it to this bug report.

You are receiving this mail because:
  • You are watching all bug changes.