Wireshark-bugs: [Wireshark-bugs] [Bug 11032] wireshark QT crashed when opening a 2G pcapng file
Pascal Quantin
changed
bug 11032
What |
Removed |
Added |
CC |
|
pascal.quantin@gmail.com
|
Comment # 4
on bug 11032
from Pascal Quantin
(In reply to Xiaochuan Sun from comment #3)
> I created a pcap file with size of 263MB, which can be opened by GTK+ based
> wireshark, but could not be opened by QT based wireshark. The QT based
> wireshark crashed when opening this pcap file.
> I compressed the pcap file to 7zip format with compressed size of 15.4 MB.
> You can download the 7zip compressed pcap file at below address:
>
> http://pan.baidu.com/s/1c08NqhU
I can open this capture with the following self-compiled Wireshark version:
Version 1.99.6 (v1.99.6rc0-4-g14c9b17 from master)
Copyright 1998-2015 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 Qt 5.4.1, with WinPcap (4_1_3), with libz 1.2.5, with
GLib 2.38.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, without PortAudio,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (with SSE4.2), with 7879MB of
physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
According to Process Explorer, it consumes 1,723,636K of virtual memory.
By comparison, the same file loaded in the GTK version of v1.99.6rc0-4-g14c9b17
consumes 1,377,732K of virtual memory.
You are receiving this mail because:
- You are watching all bug changes.