Wireshark-bugs: [Wireshark-bugs] [Bug 11280] Long delay when loading capture file
Comment # 14
on bug 11280
from Guy Harris
(In reply to Alan Bowman from comment #10)
> I copied the entire directory to a new directory (on another disk), and the
> delay persists when opening one of them.
It persists with one particular file, but not the others? Or it persists if
you open any of them?
> 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 original files had a delay when opening, but the new one didn't.
> I repeated this several times, and each time had no delay for
> 1.pcapng, but a long delay for the original file.
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?
> I tried renaming the new file again:
> 1.pcapng - no delay
> running.pcapng - no delay
> running12.pcapng - no delay
> running12_00000.pcapng - no delay
> running12_00000_00000000000000.pcapng - *** delay ***
> running12_00000_0000000000000.pcapng - no delay
> running12_00000_000000000000000.pcapng - no delay
>
> Note the number of zeroes in the last three files.
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?
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?
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?)
You are receiving this mail because:
- You are watching all bug changes.
