[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9797
Summary	Statistics - multiple Service Response Time (diameter) crashes GUI
Classification	Unclassified
Product	Wireshark
Version	1.10.6
Hardware	x86-64
OS	Windows 7
Status	UNCONFIRMED
Severity	Normal
Priority	Low
Component	Wireshark
Assignee	bugzilla-admin@wireshark.org
Reporter	nejasmicz@gmail.com

Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)

Compiled (64-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_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, with 3956MB of physical memory.

Built using Microsoft Visual C++ 10.0 build 40219

--
Calculating response time for diameter packets of a snoop with some filter
(e.g. diameter.cmd.code==280 && ip.dst_host==1.2.3.4) multiple times (first
discovered with multiple different filters, but reproducibility is also
achieved without changing it) crashes the wireshark.

Steps involved in reproducing the problem:
- load a .pcap and decode it as diameter
- statistics, service response time for diameter and apply a filter
- close the filter window, but leave the one with the statistics open
- repeat the second step
- begin closing the windows -- statistics and filter
- GUI crashes

---

      You are receiving this mail because:

• You are watching all bug changes.