Wireshark-bugs: [Wireshark-bugs] [Bug 3810] New: Wireshark window takes very long time to show u
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 4 Aug 2009 22:34:15 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3810

           Summary: Wireshark window takes very long time to show up if
                    invalid network file path is at list
           Product: Wireshark
           Version: 1.3.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: arto.pesonen@xxxxxxxxxxxxxx


Build Information:
Version 1.3.0-SVN-29225 (SVN Rev 29225 from /trunk)

Copyright 1998-2009 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.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, without Python, with GnuTLS 2.8.1, with Gcrypt
1.4.4, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 28
2009), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--
Start of Wireshark and opening of new capture file was very slow. During wait
time at startup no window was visible for long time. When capture file was
opened GUI was stuck for very long time. Same issue detected also on 1.2.1
version and SVN29270.
I debugged issue with own compilation of SVN29270 and it was caused by file
path at recent files pointing to non existing network drive. There was no
indication to user of the reason and only debugging was able to tell it. 
In my opinion recent file list handling should not access network drives.


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