Wireshark-bugs: [Wireshark-bugs] [Bug 12258] Wireshark CPU usage has dramatically increased
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 14 Mar 2016 10:56:47 +0000

changed bug 12258


What Removed Added
CC   daniel.simionov@gmail.com

Comment # 2 on bug 12258 from 
I have the same issue on Debian 8, it is using 100% from one CPU core.
Wireshark stays idle, 100% of one core utilization. I hope it helps.

I did a quick gdb session, it goes in a loop:

1380        if (!dfilter.isEmpty())
(gdb) next
1382        if (!cf_name.isEmpty()) {
(gdb) next
1403            if (start_capture) {
(gdb) next
1432            if (!start_capture &&
!global_capture_opts.default_options.cfilter) {
(gdb) next
1438        return wsApp->exec();
(gdb) next
[New Thread 0x7fffd8de0700 (LWP 16544)]
[Thread 0x7fffd8de0700 (LWP 16544) exited]
[New Thread 0x7fffd8de0700 (LWP 16577)]
[Thread 0x7fffd8de0700 (LWP 16577) exited]
[New Thread 0x7fffd8de0700 (LWP 16611)]
[Thread 0x7fffd8de0700 (LWP 16611) exited]
[New Thread 0x7fffd8de0700 (LWP 16644)]
[Thread 0x7fffd8de0700 (LWP 16644) exited]

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