File size is 20KB while in reality it is 35GB

[aybe]

So I have this unit test in Visual Studio that produces an absurd amount of data when profiled...

However, for some reason, Everything sees it only being 20KB:

Screenshot 2023-08-11 105746.png (96.43 KiB) Viewed 1542 times

Closing the software, refreshing the window or redoing the search didn't help.

But if I force rebuild the database, it then shows up as expected:

Screenshot 2023-08-11 110150.png (12.33 KiB) Viewed 1542 times

Thanks!

[void]

Thanks for the issue report aybe,

This issue should be fixed in Everything 1.5.0.1353a.

Everything 1.5.0.1353a fixes an issue with reading the file size of heavily fragmented files.

Please let me know if the issue persists with this version.



Everything will not update the file size until all handles to the file are closed.

[aybe]

I've enabled `Check for updates on startup` so that next time it'll always be on last version!

The problem is still present on latest version:

Screenshot 2023-08-11 120047.png (67.34 KiB) Viewed 1531 times

Testing a bit more, seems like it's Visual Studio's fault somehow...

If you cancel a running test, there's an outstanding handle on the file and one must log off to be able to delete it:

Screenshot 2023-08-11 111142.png (20.12 KiB) Viewed 1531 times

But if you run any test up to the end, all handles are released and Everything immediately shows the right size.

However... Explorer is able to show the right size no matter whether file is locked in some way, that's a mystery!

[therube]

(

heavily fragmented files

Contig is a utility that defragments a specified file or files. Use it to optimize execution of your frequently used files.

(Or check fragmentation of an existing file.)

Contig.exe [-a] [-s] [-q] [-v] [existing file]
Contig.exe [-f] [-q] [-v] [drive:]
Contig.exe [-v] [-l] -n [new file] [new file length]

Code: Select all

-a 	Analyze fragmentation

)

[aybe]

Not sure what I'm supposed to do with this, these files are generated on the fly and not by me.

I only use them once then delete them, i.e. once you change the profiled code they naturally become obsolete.