https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14357

            Bug ID: 14357
           Summary: Crash when opening I/O Graph
           Product: Wireshark
           Version: Git
          Hardware: x86
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: m...@moshekaplan.com
  Target Milestone: ---

Created attachment 16082
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16082&action=edit
Sample PCAP

Build Information:
git commit 731a901a3e25839ef3e0d89a0a21edc69ae474df

Wireshark 2.5.0 (v2.5.0rc0-2438-g731a901a)

Copyright 1998-2018 Gerald Combs <ger...@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 (64-bit) with Qt 5.9.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with GLib 2.54.1, with zlib 1.2.11, with SMI 0.4.8, with c-ares
1.13.0, with Lua 5.2.4, with GnuTLS 3.5.8, with Gcrypt 1.7.8, with MIT
Kerberos,
with GeoIP, with nghttp2 1.25.0, with LZ4, with Snappy, with libxml2 2.9.4,
with
QtMultimedia, with SBC, with SpanDSP, without bcg729.

Running on Linux 4.13.0-25-generic, with        Intel(R) Core(TM) i5-2500K CPU
@
3.30GHz (with SSE4.2), with 3001 MB of physical memory, with locale
en_US.UTF-8,
with libpcap version 1.8.1, with GnuTLS 3.5.8, with Gcrypt 1.7.8, with zlib
1.2.11, binary plugins supported (0 loaded).

Built using gcc 7.2.0.

--
Steps to reproduce:

1) Open PCAP. e.g.: $ ./wireshark
~/Desktop/2015-08-31-traffic-analysis-exercise.pcap

2) Click "Statistics -> I/O Graph"

3) See crash:
(process:12203): GLib-ERROR **: ../../../../glib/gmem.c:100: failed to allocate
4294967296 bytes
Trace/breakpoint trap (core dumped)

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to