Skip to content

❗ Folder Size Calculation Errors on Large Volumes #7

Description

@GhostwheeI

Description:
Folder scanning sometimes returns 0 MB or 'Invalid number' due to 32-bit integer limits or directory misreads.

Steps to Reproduce:

  • Scan deeply nested or large-volume folders
  • Observe 'Invalid number' or '0 MB' even when folders are not empty

Suggested Fix:

  • Investigate using PowerShell Get-ChildItem for folder size with simplified output
  • Consider caching results to temp file if sizes exceed 2,147,483,647 (32-bit limit)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions