http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1309
Summary: UI update can take many minutes.
Product: Wireshark
Version: 0.99.3
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: bill.ward@xxxxxxxxxxxxx
Build Information:
Version 0.99.3 (SVN Rev 19011)
Copyright 1998-2006 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 with GTK+ 2.6.9, with GLib 2.6.6, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.3.1, with ADNS, with Lua
5.1.
Running with WinPcap version 3.1 (packet.dll version 3, 1, 0, 27), based on
libpcap version 0.9[.x] on Windows Server 2003 Service Pack 1, build 3790.
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'm tracking down a problem with an http based file upload control. The trace I
am capturing is one big post to a web server (about 15,000 packets). Most of
the packets are labelled "TCP segment of a reassembled PDU" apart from the last
one which is labelled "HTTP/1.1 200OK (text/html)". This is all correct, and
Wireshark does a trully magnificent job (so much so that I feel guilty
reporting this as a bug!).
The problem is if the user selects this last packet. Wireshark seems to use the
UI thread to parse all 10,000 packets which can take many minutes. This can be
confusing as the user is unsure if Wireshark is busy or has hung.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
