pokerlad

Join Date 10/2012

Mis-sizing

Mis-sized

Is Spacemonger seeing some files as huge, when really they're zero size on disk?

Apparently my BTSync folder is 53.4 PB and a file that's 28 bytes is 20,041,764,807,114,752 bytes.

When you hover over it the correct info is displayed.

Advanced Search

Subscribe to this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,

I have forwarded your problem to Stardock Support team for their assistant. Please keep an eye on this thread for any updates. We appreciate your feedback and patient.

Basj

Stardock Community Assistant.

Successfully updated karma reason!

hmm, spacemonger is also for me reporting a few files as 0bytes, phys. size 8gb. when I deleted it, it reappeard as 32PB. Then on the next run as 8gb.

Successfully updated karma reason!

Ditto, I've noticed that all the large files seem to have the sparse attribute in the tooltip,

Physical Size does not seem to represent size on disk.

I have a file

%localappdata%\Packages\AppleInc.iTunes_nzyj5cx40ttqa\LocalCache\Roaming\Adobe\CoreSync\plugins\livetype\r

Explorer tells me Size 64.1 KB and size on disk 0.

Spacemonger lists size as 64.1 KB but Physical Size as 8.0GB

Looking through quite a lot of my files are size on disk 0 that have this 8.0Gb physical. This seems to be an overflow bug, space monger not handling zero sized files?

Successfully updated karma reason!

Quoting TankBob,

reply 3

Ditto, I've noticed that all the large files seem to have the sparse attribute in the tooltip,

Physical Size does not seem to represent size on disk.

I have a file

%localappdata%\Packages\AppleInc.iTunes_nzyj5cx40ttqa\LocalCache\Roaming\Adobe\CoreSync\plugins\livetype\r

Explorer tells me Size 64.1 KB and size on disk 0.

Spacemonger lists size as 64.1 KB but Physical Size as 8.0GB

Looking through quite a lot of my files are size on disk 0 that have this 8.0Gb physical. This seems to be an overflow bug, space monger not handling zero sized files?

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj

Stardock Community Assistant.

Successfully updated karma reason!

Hello,

Sorry to hear you are having issues. I was informed that this is known issue and has been reported internally.

Thanks

Basj,

Stardock Community Assistant.

Successfully updated karma reason!

This bug seems to be there forever and renders the Treemap pretty useless.

EDIT: Fund out you can have the tree view show the "size" instead of the "physical size" (because that is a lot more actionable) by selecting "L".

Successfully updated karma reason!

This has put me off the whole company, the fact that this problem still persists baffles me, it will soon be a year since I reported it, I suspect it existed long before that too.

Will use WinDirStat instead.

The absolute state of this! How big? When I hover Telemetry.dll shows as 318,080 bytes.

Successfully updated karma reason!

Or SequoiaView (couldn't think of the name), pretty, more basic, old, but functional.

Successfully updated karma reason!

Just installed and found this issue is still present. (Sorry if you don't want me resurrecting zombie threads.) Is there a way to access the code? I've worked with file systems in the past, so I'd be happy to submit a PR if this was open-source.

Successfully updated karma reason!

Same here, apparently this happens for this type of files:
https://stackoverflow.com/questions/58296925/what-is-zero-byte-executable-files-in-windows

Successfully updated karma reason!

I seem to be having the same problem.. the Windows Subsystem for Linux files seem to cause the problem too..

Apparently my 1TB SSD.. has space for Exobytes of Data:

Kinda makes the product useless as I cant actually use it to see real sizes..

Rather insanely.. the problem doesn't exist in the old space monger:

Successfully updated karma reason!

Ran into the same, and the problem appears to have been around for ages:

https://forums.stardock.com/489803/bug-report-dramatically-wrong-sizes-being-shown-in-windows-10

Still it doesn't get any attention. Only replies you get is when they're 'on vacation'. I'd be ashamed as a dev to keep my code out there for so long, knowing it's broken to the point of being useless - while fixing it has a clear path.

Successfully updated karma reason!