Wireshark-bugs: [Wireshark-bugs] [Bug 12460] New: GTK window hangs on dual-NIC burst of DNS req/
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 20 May 2016 00:44:20 +0000
Bug ID 12460
Summary GTK window hangs on dual-NIC burst of DNS req/resp pkts from another Wireshark resolving 1500 IPs
Product Wireshark
Version 2.1.x (Experimental)
Hardware x86
OS Windows Server 2008
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter starlight@binnacle.cx 

Build Information:
Version 2.1.0-git (v2.1.0rc0-2960-gcb2627c from master)

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares
1.11.0, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built May  9 2016), with AirPcap.

Running on 64-bit Windows Server 2008 Service Pack 2, build 6002, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz (with SSE4.2), with 6133MB of
physical memory.

Built using Microsoft Visual C++ 12.0 build 40629
--
This started happening when latest libcares 1.110 was applied to 1.12.11
Wireshark and then 1500+ IPs are resolved at once while loading a PCAP.

Is very easy to produce when the monitoring Wireshark is 1.12.11, but I had it
happen a couple of times now after switching the second Wireshark to
v2.1.0rc0-2960 running the -gtk.exe.  Seems to be the same bug either way, so
I'd recommend figuring it out with the older version.  Probably fattening code
paths in the newer version reduces the probability of triggering it.

My impression is it's a race-conditon lock-up of some sort resulting from
reading two GBE Intel NICs where the DNS resolver traffic is alternating across
the two per the new libcares load balancing.

Auto-scroll enabled and seems to matter.  v2 Wireshark has a tendency to turn
it off when the window gets busy--is annoying.

Usually the hang occurs when the window is minimized.

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