[FIXED] "everything" sometimes calculates occupied space completely wrong

[jazmomo]

1. example:

those 3 folders actually are completely empty after i moved a lot of jpegs to another folder

2. example: (screenshot within total commander to make it easier visible, space is calculated by "everything".


also, once moved the whole content of a folder to another one, and instead "zero", "everything" showed negative numbers.

this happened many times now here, on external hard disks.
Win 7
external USB drive, encrypted by Verycrypt (NTFS)
Everything 1.4.1.877 32bit


only rebuilding the database helps.

[therube]

Does the Tracks directory contain "links" of some sort (or junctions)?

Does this occur only on the encrypted drive?
Does this occur on all directories on the encrypted drive or only some?


Is your screenshot also showing that the TC directory calculation is also incorrect?

[jazmomo]

1) they are plain directories with absolutely nothing in them.

2) hard to tell, my system disk is small, the others all encrypted. i will keep an eye on it.

3) only on very few. so its' (unfortunately) kinda hard to reproduce. but it seems to happen if there's a lot of activity in a directory, lets say unpacking lots of files using a simple batch script.

[jazmomo]

ok, checked it. it happens on my un-encrypted system drive too.

i could easily reproduce this time:

but it seems to happen if there's a lot of activity in a directory, lets say unpacking lots of files using a simple batch script.

what i did. had lots of ZIP files (a directory with 2 subdirectories), unpacked them via batch (ended up with 8500 files), deleted the zips, moved the 8500 files to another directory (same drive). et voilà... same as in picture 1, both the now empty subdirectories are calculated wrong.

but when i move those 2 subdirs to another place as well, "everything" seems to be fine again.

[void]

If the issue is reproducible could you please send some verbose debugging information:

• In Everything, type in the following search and press ENTER:
  /verbose
• Type in the following search and press ENTER:
  /debug
• Reproduce the issue.
• Please send the debug output to support@voidtools.com

[jazmomo]

i will do so, next time i have to unpack a bunch of files.

[void]

Please try Everything 1.4.1.885.

Everything 1.4.1.885 fixes a bug where not all file sizes are calculated correctly after renaming a folder.

Everything-1.4.1.885.x86.zip
Everything-1.4.1.885.x64.zip

[jazmomo]

cool, thanks.

it wasn't as easy to reproduce as expected. it happened again here and there, but never when it was in /debug mode. and as soon as i noticed it was too late, the debug window output buffer was overwritten with newer stuff.
i even packed and unpacked hundreds of small jpg files in a test folder, but no problems there.

i wonder if this really happens only here? i am using the x86 version because it eats less RAM, which is a good thing on my older notebook.
but maybe i should try the x64 version too. although, i doubt it would make a difference.

[jazmomo]

so far it looks good, let's keep fingers crossed.

[jazmomo]

still fine.

sorry for spamming, but i'm still not 100% sure, although it should be ok now.

[jazmomo]

sorry to say, but this bug is back since about 1.4.1.909

[void]

A couple questions:
Does this occur often?
Does the incorrect folder size go all the way back to the C: drive? (eg: if you search for root: is the size of your C: massive?)
Are you using NTFS or FOLDER indexing?
Do you have any exclude options enabled?

[jazmomo]

sorry, i'm an idiot. it is not the same issue.

it's more the other way now, everything is MISSING big files.

.906 works fine, after .908+ has this issue, i might also try .907
and yes, it happens often.
i have some excludes, but only whole drives.

i will do some more testing.

[void]

Please try Everything 1.4.1.914.

Everything 1.4.1.914 addresses an issue with reading large file sizes.

[jazmomo]

i've seen this before and i tried it, unfortunately it did not solve the issue for me. but i gave it a try again with .915, no luck again.
but yes, it's the bigger files that have "no size" in everything.
only rebuilding the database helps, but this is not exactly a solution.


i will try .907 now


/edit: up to .907 this works fine.

[void]

Could you please send some debug output from Everything 1.4.1.914:

• In Everything, type in the following search and press ENTER:
  /debug_log
• Reproduce the issue.
• Please send your %TEMP%\Everything Debug Log.txt to support@voidtools.com

Please avoid using Everything 1.4.1.915 as it has service debug logging enabled and will drastically effect performance.

[jazmomo]

done.

thanks for taking your time!

[void]

Everything 1.4.1.916 should fix the issue:

Fixed an issue with reading large file sizes.

[jazmomo]

yes, it does work now properly, thanks a lot!