Wireshark-bugs: [Wireshark-bugs] [Bug 12035] New: Wireshark QT hangs when stopping the capture
| Bug ID |
12035
|
| Summary |
Wireshark QT hangs when stopping the capture
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
CONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
45t7efgg2q@snkmail.com
|
Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)
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 WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10586, with locale C, 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-5500U CPU @ 2.40GHz (with SSE4.2), with 8114MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
When I after running a capture stop the capture, Wireshark sometimes (pls see
'Note' below) hangs forever and uses a lot of resources. I therefore used the
Sysinternals process monitor and can see that Wireshark keeps trying to read
from the
"C:\Users\<my-usrid>\AppData\Local\Temp\wireshark_2_interfaces_20160119234912_a10072"
and keeps getting "END OF FILE".
When I try the same thing with Wireshark-gtk.exe (Legacy) from the same install
this problem does not happen.
Note: A circumvention for this problem seems to be : Create a new profile
before starting each new capture (and only use the profile once - the same
profile might work several times, but when a profile start failing once it keep
failing).
You are receiving this mail because:
- You are watching all bug changes.
