Wireshark-bugs: [Wireshark-bugs] [Bug 10489] New: "Stop and save" crashes if nothing was capture
Date: Sat, 20 Sep 2014 21:23:17 +0000
Bug ID 10489
Summary "Stop and save" crashes if nothing was captured
Product Wireshark
Version 1.12.1
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter dpb@corrigendum.ru

Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> 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.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 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.1.22, Gcrypt 1.6.0, without AirPcap.
       Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, with 8147MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
Start a packet capture and make sure that no packets are captured (e.g. with an
impossible filter). Then try to close the window. The standard "do you want to
save" dialog pops up. If you click "Stop and Save", Wireshark crashes.


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