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

            Bug ID: 13174
           Summary: Export Objects dialog in GTK crashes due to wrong
                    memory scope
           Product: Wireshark
           Version: 2.2.2
          Hardware: x86
                OS: All
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: GTK+ UI
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: mman...@netscape.net

Created attachment 15085
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15085&action=edit
Sample capture used to reproduce bug

Build Information:
Version 2.2.2 (v2.2.2-0-g775fb08)

Copyright 1998-2016 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 GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares
1.12.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 16 2016), with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, 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-6820HQ CPU @ 2.70GHz (with SSE4.2), with 32590MB of
physical memory.
--
Using Export Objects dialog in GTK crashes due to the fact that it's trying to
free file_scoped() memory from pointers that were g_ allocated.
Discovered on master branch, verified on 2.2.2 release.

Looks like there also may be a memory leak in Qt version because I don't see
any attempt to free the same structures that are causing crashes in GTK.

-- 
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