| Bug ID |
11756
|
| Summary |
Qt UI on Windows crashes when changing to next capture file
|
| Product |
Wireshark
|
| Version |
2.0.0
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)
Copyright 1998-2015 Gerald Combs <[email protected]> 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 7 Service Pack 1, build 7601, 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-5600U CPU @ 2.60GHz (with SSE4.2), with 16272MB of
physical
memory.
--
Based on a recent Q&A question I tried using the ring-buffer-mode options in
the Qt UI.
Wireshark consistently crashes when it's time to change files.
I tried to reproduce this on Linux but was unable to (admittedly I may not have
been at 2.0.0 though I tried both master and master-2.0) so I won't be much
help fixing it.
How to reproduce:
1) Go to the Capture Options dialog.
2) Select an input interface
3) Go to the Output tab
4) Fill in a file name (I used "c:\tmp\foo")
5) Select "Create a new file automatically after..."
6) Select 5 seconds (using capture file size also works but obviously it
requires some traffic)
7) Start the capture
8) After 5 seconds, Wireshark will crash.
Note: this is a new installation; I don't think I've changed any preferences
yet.
The Gtk+ UI (also v2.0.0) does not have this problem.
You are receiving this mail because:
- You are watching all bug changes.
