Wireshark-bugs: [Wireshark-bugs] [Bug 3810] Wireshark window takes very long time to show up if
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3810
--- Comment #4 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-07-07 13:49:28 PDT ---
(In reply to comment #3)
> If Wireshark can identify the file as "not found", it must have tried to look
> for it.
Yes, it did.
> I would expect it to be removed from the list at that point
Well, if the file is on a network share, it might become available again, so
removing it from the list might not be desirable for everyone.
> but I don't understand why Wireshark looks for the file
> in the first place.
Wireshark tries to stat() the file so it can also display the file size in
parenthesis after the file name, but since it knows the file is inaccessible,
it will not make it selectable.
> Shouldn't the Open Recent just be a static list of files
> and Wireshark would only attempt to look for/open the file if selected?
Arguably, yes.
> IMO it shouldn't cache the file's availability.
Well, it's not cached per se. The stat() is performed each time Wireshark is
started, so a file previously not accessible could be accessible the next time
Wireshark is started or vice versa.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
