superfile

Upgrade Superfile to a release containing the fix for issue #1550 (fix(metadata): gate binary architecture detection behind magic-byte check). In v1.6.0, GetBinaryArchitecture runs on every regular file and calls elf.Open, then pe.Open, then macho.Open. Go's debug/pe accepts files without an MZ header as raw COFF objects, so video data can be misparsed, causing multi-GB heap allocations that are not released until exit. The fix checks the file's magic bytes before attempting ELF/PE/Mach-O parsing. As a temporary workaround on v1.6.0, avoid sweeping or bulk-selecting many large video files for metadata/thumbnail extraction and restart Superfile to release the retained memory.

On Linux/Unix, FileInfo.Size() for a directory returns the size of the directory inode/entry block (commonly 4 KiB), not the recursive size of its contents. superfile's metadata panel used this value unconditionally, producing a misleading folder size. The fix treats directories separately and no longer displays the inode size as the folder size. Update superfile to the latest release—for example, go install github.com/yorukot/superfile@latest or use your package manager's upgrade command—and restart it. To obtain the actual total size from a shell, run du -sh /path/to/folder (or du -sh --apparent-size /path/to/folder for apparent size).