| Bug ID |
12857
|
| Summary |
Wireshark becomes unresponsive while capturing packets.
|
| Product |
Wireshark
|
| Version |
2.2.0
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14896 [details]
Slow loading packet trace and .png of configuration
Build Information:
Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)
Copyright 1998-2016 Gerald Combs <[email protected]> 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 Qt 5.3.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10586, 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) i7-3770 CPU @ 3.40GHz (with SSE4.2), with 16338MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
While attempting to trace browser access to
http://journaldev.us8.list-manage1.com/track/click?u=612f3d966c86000f37699d8cf&id=9789c2e700&e=bc884fdbb6
wireshark becomes unresponsive. It's not hung since if you wait long enough
(several minutes) you can get responses to clicks. I saved a session (3758
packets) where this was happening. When you try to load this saved session
back into wireshark, the load process takes 5-6 minutes. I have no reason to
think that the particular URL I used is significant.
I've attached a zip file with the saved packets and a .png file that shows my
system configuration. Let me know if there's more that I should send.
Thanks.
PS Ignore the "component" field in the report. I have no idea where the
problem is.
You are receiving this mail because:
- You are watching all bug changes.