(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 months agoefficient game design rulelemmy.blahaj.zoneimagemessage-square47fedilinkarrow-up1746arrow-down116
arrow-up1730arrow-down1imageefficient game design rulelemmy.blahaj.zone(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 months agomessage-square47fedilink
minus-squarertxn@lemmy.worldlinkfedilinkEnglisharrow-up30·2 months agoIt’s possible that the log writer wanted to fseek to the end of the file and write something, but the target pointer value was somehow corrupted. Depending on the OS, the file might end up having a fuckton of zeroes in the skipped part.
minus-squareTheEntity@lemmy.worldlinkfedilinkarrow-up11arrow-down1·2 months agoThat should result in a sparse file on any sane filesystem, right?
minus-squarertxn@lemmy.worldlinkfedilinkEnglisharrow-up9·2 months agoTheoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
minus-squareThe_Decryptor@aussie.zonelinkfedilinkEnglisharrow-up2·2 months agoIt supports it, but it’s opt-in by apps. Enabling compression is another option (Though with a speed and size penalty), it’s user visible at least.
It’s possible that the log writer wanted to
fseekto the end of the file and write something, but the target pointer value was somehow corrupted. Depending on the OS, the file might end up having a fuckton of zeroes in the skipped part.That should result in a sparse file on any sane filesystem, right?
Theoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
It supports it, but it’s opt-in by apps.
Enabling compression is another option (Though with a speed and size penalty), it’s user visible at least.