Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12494] New: Wireshark crashes during capture

Date: Tue, 07 Jun 2016 11:23:31 +0000
Bug ID 12494
Summary Wireshark crashes during capture
Product Wireshark
Version 2.0.3
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Critical
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Created attachment 14616 [details]
Crash logs

Build Information:
Version 2.0.3 (v2.0.3-0-geed34f0 from master-2.0)

Copyright 1998-2016 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-2620M CPU @ 2.70GHz (with SSE4.2), with 8079MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

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 capturing data und clicking the green button to restart current capture
the whole program crashes. This is reproducible.
Also, when I capture data, click on Stop and then the blue button to start a
new caputre, the program crashes also.

The crash logs of these issues I had in the past weeks are attached.


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