| Bug ID |
10718
|
| Summary |
"Closing File" Message Hangs Under certain conditions
|
| Product |
Wireshark
|
| Version |
1.12.2
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.2 (v1.12.2-0-g898fa22 from master-1.12)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 12 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, with 8123MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
I run the same tests for each release before approving the release for use in
my company. 1.12.1 is currently in use.
Testing 1.12.2 reveals a consistent issue with the "Closing File" warning
window hanging if the following conditions are met:
1) Capture options have all check boxes unchecked except for NG format
2) After starting the capture, minimize both the main window and the Captured
Packets window
3) Allow the capture to extend to a few hundred million bytes of data captured
4) Activate the minimized Captured Packets window and press Stop
At this point the "Closing File Please wait ..." window is stuck.
If I go to the task bar and click on the red "x" in the upper right of the
preview window for the "Closing File" window, the capture file is usable in the
main capture window - no problems.
The problem is consistent with this release if the above steps are followed.
If either of the windows is NOT minimized, the problem is circumvented.
Of course if I could convince everyone to use DUMPCAP you would not be reading
this!:)!
You are receiving this mail because:
- You are watching all bug changes.