https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7610
--- Comment #4 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2012-09-12 04:31:07 PDT ---
(In reply to comment #3)
> I have same problem crashing Wireshark caused by VC++. This happens with
> different capture files. These files have a size between 20 MByte and 100
> MByte.
> Also, this happens on two different machines. A notebook with Core i7 Quad (3rd
> Gen.) and 8GB of RAM and on a Desktop machine with Core i7 (2nd Gen.) and 16 GB
> of RAM. Both are running Win 7 x64 Pro.
> Wireshark process uses much less than 2GB RAM before crashing. This mostly
> happens while filtering or opening the IO-graph.
> ______________________________________________________________________________
> 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 (64-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, without Kerberos, with GeoIP, with PortAudio
> V19-devel (built Aug 15 2012), with AirPcap.
> Running on 64-bit Windows 7 Service Pack 1, build 7601, 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, with AirPcap 4.1.1 build
> 1838.
> Built using Microsoft Visual C++ 10.0 build 40219
Hi,
Could you try a recent development build from
http://www.wireshark.org/download/automated/win64/
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.