• mogoh@lemmy.ml
      2·
      2 months ago

      It is also something that can happen easily. Just program to log an error and then the error happens unexpected every frame.

      • dustyData@lemmy.world
        1·
        2 months ago

        It’s a crash log, not an error log. It’s probably dumping the entire memory stack to text instead of a bin dump every time it crashed. I would also suspect the crash handler is appending to the log instead of deleting old crashes and just keeping the latest. At several dozen gigas of RAM it would just take a couple of game crashes to fill up the 300GB.

  • yetAnotherUser@discuss.tchncs.de
    0·
    2 months ago

    Ok, but the second tweet is a bit redundant

    Like what else would a .log file be? A video file? A Word Document? An executable?

    Do you really need to inspect the properties to be told: “This .log file is certainly containing text. Thank you for installing Windows 10. Save 5% on your Office 365 subscription with code ‘ILOVEMICROSOFT’”

    • MirthfulAlembic@lemmy.worldEnglish
      1·
      2 months ago

      It could be a binary file, though that would probably make it smaller if anything.

      I’m guessing the point was the developer didn’t invent some proprietary log that also contained a dump and other things that could conceivably be very large. That would also be terrible design, but managing to create hundreds of gigs of text in a game crash log is a special kind of terrible.

  • Donebrach@lemmy.world
    0·
    2 months ago

    I played this game start to finish on PC (A Frankenstein-esquire gaming rig)—never had this issue. I am guessing this is a made-up problem or just someone trying to run this game on a computer that is not capable of running it. a lot of people assume because they “have a pc” they can just run the latest and greatest game. Dude’s probably on his work issued thinclient trying to boot up a modern AAA game with basic-ass virtual resources and are like “huh?” when it doesnt work.

    • thepreciousboar@lemm.ee
      1·
      2 months ago

      No crash log, under any circumstance, regardless of available resources, should reach 300GB. No useful information can be gathered and it probably meana the program was running an infinite loop.