(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 14 hours agoefficient game design rulelemmy.blahaj.zoneimagemessage-square36fedilinkarrow-up1575arrow-down112cross-posted to: microblogmemes@lemmy.world
arrow-up1563arrow-down1imageefficient game design rulelemmy.blahaj.zone(⬤ᴥ⬤)@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 14 hours agomessage-square36fedilinkcross-posted to: microblogmemes@lemmy.world
minus-squaremogoh@lemmy.mllinkfedilinkarrow-up41·13 hours agoYeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
minus-squarertxn@lemmy.worldlinkfedilinkEnglisharrow-up28·12 hours 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·12 hours agoThat should result in a sparse file on any sane filesystem, right?
minus-squarertxn@lemmy.worldlinkfedilinkEnglisharrow-up7·12 hours agoTheoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
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.