https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4711
Summary: After running a trace overnight Wireshark stops
responding
Product: Wireshark
Version: 1.2.7
Platform: Other
OS/Version: Windows 7
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: bigmags@xxxxxxxxx
Build Information:
Version 1.2.7 (SVN Rev 32341)
Copyright 1998-2010 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 with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8,
with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 31 2010), with
AirPcap.
Running on 32-bit Windows 7, build 7600, with WinPcap version 4.1.1 (packet.dll
version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I ran a trace (numerous times over numerous days) overnight with multiple files
or as one file. Sometime overnight Wireshark stops responding and I need to
close the program and I found it in this state when I return in the morning to
check the trace.
Is there a fix for this yet? If not, please look into this and come up with
one. I need to run Wireshark for long periods of time to track down a bug in my
product firmware that is intermittent and does not happen often.
Thanks,
Martin
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
