Wireshark-bugs: [Wireshark-bugs] [Bug 13095] New: Wireshark 2.0.4 Crashes on Windows 10/7 in Liv
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 04 Nov 2016 16:11:23 +0000
Bug ID 13095
Summary Wireshark 2.0.4 Crashes on Windows 10/7 in Live Capture Analysis using live interfaces/remote capture interfaces
Product Wireshark
Version 2.0.4
Hardware x86
OS Windows 10
Status UNCONFIRMED
Severity Minor
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter sadu.dinesh87@gmail.com 

Created attachment 15042 [details]
gmemc issue and wireshark-gtk crash

Build Information:
Version 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)

Copyright 1998-2016 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 (32-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
WinPcap (4_1_3), with libz 1.2.8, with GLib 2.38.0, with SMI 0.4.8, with c-ares
1.11.0, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Jun  7 2016), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, 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) i5-3470 CPU @ 3.20GHz (with SSE4.2), with 8066MB 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.
--
Hi,

I am eagerly waiting for fix gmem.c issue because this as i am unable to run
the tool for more long hours (>5+ hrs) for performing live/remote capture
analysis.

Capturing TCP Traffic Packets, I found crash after 300000+  Lakh TCP Packets.

We use capture for more than 8 hours using Wireshark-1.6.x release.
But now we are observing crash for less than 2 hours using wireshark 2.x.x

Thank you.

Regards,
Dinesh Sadu

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