Wireshark-bugs: [Wireshark-bugs] [Bug 13167] New: Wireshark stops responding while capturing thr
| Bug ID |
13167
|
| Summary |
Wireshark stops responding while capturing through pipe interface
|
| Product |
Wireshark
|
| Version |
2.0.4
|
| Hardware |
x86
|
| OS |
Windows 8.1
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
raja.massand@mindtree.com
|
Created attachment 15084 [details]
Screenshot
Build Information:
Wireshark 2.0.4 (Git Rev Unknown from unknown)
Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with libz 1.2.8, with GLib 2.42.0, with SMI 0.4.8, with c-ares
1.11.0, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Nov 23 2016), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz (with SSE4.2), with 7997MB of
physical memory.
Built using Microsoft Visual C++ 11.0 build 61030
--
As Wireshark is initialized to capture packets from pipe interface, the
application stops responding as an when some initial packets are logged. User
is unable to see any information in packet details pane and packet bytes pane.
This bug is observed when any of following layout is selected:Wireshark starts
responding as and when some more packets are logged.
-> layout_type_5
-> layout_type_2
-> layout_type_1
-> layout_type_3
This bug is not observed when any of following layout is selected:
-> layout_type_4
-> layout_type_6
You are receiving this mail because:
- You are watching all bug changes.
