Wireshark-bugs: [Wireshark-bugs] [Bug 11529] New: Wireshark hangs (Not responding) when I filter
Date: Wed, 16 Sep 2015 16:01:11 +0000
Bug ID 11529
Summary Wireshark hangs (Not responding) when I filter a TCP stream
Product Wireshark
Version 1.12.7
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Critical
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter zxcasd059@gmail.com

Created attachment 13872 [details]
Wireshark capture file zipped

Build Information:
Version 1.12.7 (v1.12.7-0-g7fc8978 from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Aug 12 2015),
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 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz, with 12287MB of physical memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
1) Open the attached trace file 
2) Apply filter tcp.stream eq 27
3) Wireshark goes into "Not responding"
4) The bug was reproducible using Mac OS X Wireshark also.
5) Captured another capture in TCP dump format and still the bug is
reproducible.

I am trying to workaround using MS network monitor but it sucks.


You are receiving this mail because:
  • You are watching all bug changes.