Wireshark-bugs: [Wireshark-bugs] [Bug 5109] New: Backward searches (Find Previous, Find>Up) in c
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 12 Aug 2010 15:13:26 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5109

           Summary: Backward searches (Find Previous, Find>Up) in
                    compressed captures is extremely slow
           Product: Wireshark
           Version: unspecified
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: turney_cal@xxxxxxx


Build Information:
Version 1.4.0rc2 (SVN Rev 33665 from /trunk-1.4)

Copyright 1998-2010 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 with GTK+ 2.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jul
28 2010), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--
This problem is not specific to any particular Wireshark version.  To reproduce
the issue open a zip'd or gzip'd capture that has at least 100K uncompressed
and has a compression ratio of 2:1 or better. Mark the first and last frame,
then go to the frame 1 and search forward to the next mark. This It should not
take very long.  Then search backward for the next mark.  The progress bar will
appear but it might take minutes for anything to happen.  In a few cases with
captures that were double the size of the above or more, Wireshark crashed.  

I've uploaded a capture to
"ftp://ftp.emc.com/pub4/centera_tools/GNS/compressed.cap.gz"; which is 40MBs
compressed and 146MB uncompressed which can be used for testing.

I don't know if this issue also occurs in Linux and OSX versions.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.