Wireshark-bugs: [Wireshark-bugs] [Bug 7028] New: Crash when reassembling LARGE xml data
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7028
Summary: Crash when reassembling LARGE xml data
Product: Wireshark
Version: 1.6.6
Platform: x86-64
OS/Version: Windows 7
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: me@xxxxxxxxxxxx
Build Information:
Version 1.7.0 (SVN Rev 39768 from /trunk)
Copyright 1998-2011 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.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (version unknown), 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.10.3, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Nov 8 2011), with AirPcap.
Running on 64-bit Windows 7, build 7600, 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.10.3, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 21022
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I am calling a web service, which (apparently) returns a *massive* amount of
data. HTTP response header indicates a content length of 17,779,043.
When attempting to reassemble the HTTP response, WireShark crashes.
This issue occurs in both 1.6.6 and 1.7.0.
In 1.6.6, I received an error that looked something like: dissector bug
protocol xml more than 1000000 items in the tree
in 1.7.0, I get a simple MFC error.
I have identified that the bug is not in the capture, but rather in the
reassembly... WireShark freezes not immediately when the call returns, but
rather a few seconds after... additionally, I used Network Monitor to capture
(which worked fine, but their UI blows, and I can't find a way to reassemble),
but loading the capture file into wireshark causes the same crash.
This appears in the windows event logs:
Faulting application name: wireshark.exe, version: 1.7.0.39768, time stamp:
0x4eb990e8
Faulting module name: libglib-2.0-0.dll, version: 2.26.1.0, time stamp:
0x4d1b271d
Exception code: 0x40000015
Fault offset: 0x000000000005180e
Faulting process id: 0x20d0
Faulting application start time: 0x01cd11b455b71bc0
Faulting application path: C:\Program Files\Wireshark\wireshark.exe
Faulting module path: C:\Program Files\Wireshark\libglib-2.0-0.dll
Report Id: 9c55379b-7da7-11e1-ba75-782bcb944eb3
I wish I could attach the capture file, but it does contain sensitive
information.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
