Wireshark-bugs: [Wireshark-bugs] [Bug 11280] Long delay when loading capture file
Comment # 16
on bug 11280
from Alan Bowman
(In reply to Guy Harris from comment #14)
> It persists with one particular file, but not the others? Or it persists if
> you open any of them?
I picked one file at random from the directory, and it had the delay upon
opening. I tried with several files, one at a time, selected randomly. All
had the delay.
> > I copied one of the files, and named it "1.pcapng" (so very different name
> > from previously).
>
> So is the copy in the same new directory?
The copy is in the same directory as all the other files.
> So you have, in that directory, two files with the exact same content, and
> the file with the original name, matching the
> runningxx_yyyyy_zzzzzzzzzzzzzz.pcapng pattern, has a long delay, but the
> identical copy, with the name 1.pcapng, doesn't?
Correct.
> So files that have names that match the pattern
> runningxx_yyyyy_zzzzzzzzzzzzzz.pcapng have a delay, but other files don't?
>
> And changing the "r" in "running" to "R" gets rid of the delay?
Correct.
> Does this happen if you open the file by double-clicking on it, or does it
> only happen when opening through the File -> Open dialog or the recently
> used menu?
This happens both when I select the file by double clicking in Windows Explorer
to autostart Wireshark, and by selecting it in File->Open... and by selecting
it from the Recently opened list.
> What type of file system is on that disk - FAT of some flavor, NTFS, ReFS,
> or something else? (I'm assuming this is a local disk rather than a volume
> from a server; if it's from a server, what protocol is being used - SMB,
> SMB2, or something else - and what OS is the server running?)
It's a local disk, NTFS I believe.
You are receiving this mail because:
- You are watching all bug changes.
