• 9point6@lemmy.world
    link
    fedilink
    arrow-up
    71
    arrow-down
    2
    ·
    edit-2
    2 months ago

    So

    300×1024×1024= 314,572,800kb

    Assuming something like 200 bytes per log line

    x5 = 1,572,864,000 logs

    Assuming this is your standard console port with a 60fps frame rate lock:

    ÷60fps ÷ 60 seconds ÷ 60 minutes ÷ 24h = 303.407… days

    You would need to play for nearly a year solid to generate that many logs at a rate of one per frame.

    Given that’s probably not what’s happened, this is a particularly impressive rate of erroring

    • mogoh@lemmy.ml
      link
      fedilink
      arrow-up
      50
      ·
      2 months ago

      Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.

      • rtxn@lemmy.world
        link
        fedilink
        English
        arrow-up
        30
        ·
        2 months ago

        It’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.

          • rtxn@lemmy.world
            link
            fedilink
            English
            arrow-up
            9
            ·
            2 months ago

            Theoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.