https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7783
Summary: The capture crashes after time with Visual C++ error
Product: Wireshark
Version: 1.8.2
Platform: x86
OS/Version: Windows Server 2003
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: csmith@xxxxxxxxxxxxxx
Build Information:
Version 1.8.2 (SVN Rev 44520 from /trunk-1.8)
Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Aug 15 2012), with AirPcap.
Running on Windows Server 2003 Service Pack 2, build 3790, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap, from the
PortableApps U3 device in drive C:.
Built using Microsoft Visual C++ 10.0 build 40219
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 doing a filtered capture (removing a small subnet and email traffic) the
capture is setup to do 100x100mb ring buffer. It might get to 40 - 50 files
before it crashes. I have tried different buffer size, different file size,
different storage, ran it on a VM. It always crashed. From what I can tell, the
ram isn't being abused. Before and after the crash it shows the same basic
usage.
I disable screen updates, and resolution of names.
I am trying to do a continual capture.
Clayton
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.