| Bug ID |
8273
|
| Summary |
Changing configuration profile causes packet display to be processed multiple times
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.9.x (Experimental)
|
| Hardware |
x86
|
| OS |
Windows Vista
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.9.0-SVN-47367 (SVN Rev 47367 from /trunk)
Copyright 1998-2013 Gerald Combs <[email protected]> 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jan 29 2013), with AirPcap.
Running on 32-bit Windows Vista Service Pack 2, build 6002, without WinPcap,
GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 10.0 build 40219
--
If I have a large trace file loaded and change configuration profiles, the
"Reprocessing: all packets" dialog will pop up multiple times. It will open,
complete the packet processing, close, and then immediately reopen and process
all packets again. The behavior is somewhat erratic. Usually the dialog will
pop up three times consecutively, but occasionally it will pop up four times,
and sometimes only one time. If I keep changing profiles, Wireshark will
eventually crash.
I see this behavior on my Windows Vista PC with both the PortableApps version
of Wireshark and the regular (non-PortableApps) 32-bit version, and also on my
Windows 7 laptop with the 64-bit version.
I was able to reproduce this behavior consistently with a 35 MB trace file
containing 37,000 packets. It doesn't appear to occur as often with small trace
files, but it may be that the dialog is opening and closing too quickly to be
seen.
You are receiving this mail because:
- You are watching all bug changes.