Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12291] New: Unable to open pcap file, Wireshark just stops responding and the

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12291
Summary	Unable to open pcap file, Wireshark just stops responding and the memory for process keeps increasing
Product	Wireshark
Version	unspecified
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Capture file support (libwiretap)
Assignee	bugzilla-admin@wireshark.org
Reporter	jkshar2005@gmail.com

Build Information:
C:\Program Files\Wireshark>

Wireshark 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later <http://www.gnu.org/licenses/old-lic
nses/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-4600U CPU @ 2.10GHz (with SSE4.2), with 8097MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 31101
--
I am trying to open a file which is around 24 MB and wireshark just sits with
its process just taking CPU and memory which increase over time.

Running Windows 7 64 bit with 8 GB of RAM.

---

      You are receiving this mail because:

• You are watching all bug changes.