Bug ID: 14527
           Summary: dumpcap processes cannot be killed after forcibly
                    killing wireshark
           Product: Wireshark
           Version: 2.4.5
          Hardware: x86-64
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Critical
          Priority: Low
         Component: GTK+ UI
  Target Milestone: ---

Build Information:
Compiled (64-bit) with Qt 5.6.3, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
SBC, with SpanDSP.

Running on 64-bit Windows 10, build 14393, with Intel(R) Xeon(R) CPU E5-1620 v3
@ 3.50GHz (with SSE4.2), with 16306 MB of physical memory, with locale
English_United States.1252, with Npcap version 0.99-r1, based on libpcap
1.8.1, with GnuTLS 3.4.11, with Gcrypt 1.7.6, without AirPcap.

Built using Microsoft Visual C++ 14.0 build 24215
Windows 10 (x64)

- Close all existing wireshark windows
- In Windows Explorer, select 2 .pcap files
- Press ENTER to open them and wireshark hangs
- Manually kill wireshark
- After wireshark killed, 6 dumpcap processes still kept running and cannot
  be killed. And wireshark would refuse to uninstall itself. The computer has
  to be restarted to solve this.

Page also
reports the same problem on Windows 8.1 with wireshark 2.4.3. According to this
page "i noticed if i select multiple trace files in windows explorer, there is
a 90% chance that Wireshark will hang while loading."

You are receiving this mail because:
You are watching all bug changes.
Sent via:    Wireshark-bugs mailing list <>

Reply via email to