| Bug ID |
11280
|
| Summary |
Long delay when loading capture file
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.99.7-193-g75ddc45 (v1.99.7rc0-193-g75ddc45 from master)
Copyright 1998-2015 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.1, with WinPcap (unknown), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, without PortAudio,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Xeon(R) CPU W3530 @ 2.80GHz (with SSE4.2), with 6141MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
When I load a capture file (typical ~1MB, 16000 packets of ZigBee traffic),
there is a long period when Wireshark is "Not Responding". Using Resource
Monitor, I can see a brief period of disk activity (~3 seconds) then over a
minute when one of my CPUs is fairly fully loaded, but there is no response
from Wireshark.
When I load the same file in Wireshark Legacy, the application is responsive
almost immediately.
You are receiving this mail because:
- You are watching all bug changes.