Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6644] When capturing, wireshark GUI use 100% cpu and appea

Date: Mon, 16 Jul 2012 22:09:05 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6644

Juan Guerra <a123a654a789@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |a123a654a789@xxxxxxxxx

--- Comment #4 from Juan Guerra <a123a654a789@xxxxxxxxx> 2012-07-16 22:09:04 PDT ---
It also happens to me after updating from Ubuntu 10.04 to 12.04 (present
Wireshark version is 1.6.7, the previous one could be 1.6.4, but I'm not sure).

It only happens on live capture. When I start it, it uses normal CPU, and if
the traffic is slow, it continues like before, but after some time or if the
traffic increases, then Wireshark consumes 100% CPU and freezes until has
processed every packet, which takes too much than previously and depending on
the data received could be some minutes or hours. After that, if network
traffic stops, Wireshark does not use CPU, but when traffic starts again, also
starts the 100% CPU consuming.

But the most curious thing is that previously, when I had just updated to
Ubuntu 10.04, it had been happening this same problem for some months and some
day I realized it worked well! I don't know exactly when because I stopped
using it because of the problem, but it had to be some Ubuntu update, but not
to the Wireshark package, which they never updated. So, because of that, and
some analysis some friends help me made of it, I think the problem is related
to the gtk library which shows the list of packets. But the problem is unique
to Wireshark.

Dumpcap works well, it's the Wireshark (GUI) process using 100% CPU.

That's all I can say about this problem, if you want more information, ask me
and I will try to provide it to you.
Please fix this, as zebulon said, it is unusable for live capturing.

Here is also the Build Information:
Version 1.6.7

Compiled (64-bit) with GTK+ 2.24.10, with GLib 2.32.0, with libpcap (version
unknown), with libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre,
with SMI 0.4.8, with c-ares 1.7.5, with Lua 5.1, without Python, with GnuTLS
2.12.14, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Dec 10 2011 11:43:10), without AirPcap.

Running on Linux 3.2.0-26-generic, with libpcap version 1.1.1, with libz
1.2.3.4, GnuTLS 2.12.14, Gcrypt 1.5.0.

Built using gcc 4.6.3.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.