• 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’”

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

      I think their point is that a 200gb text file is a wild size usage for a crash log, and there’s probably accidentally some binary data in that log. There’s no way a crash log can exceed 2x the size of the game binary itself.

    • You should have rolling log files of limited size and limited quantity. The issue isn’t that it’s a text file, it’s that they’re not following pretty standard logging procedures to prevent this kind of thing and make logs more useful.

      Essentially, when your log file reaches a configured size, it should create a new one and start writing into that, deleting the oldest if there are more log files than your configured limit.

      This prevents runaway logging like this, and also lets you store more logging info than you can easily open and go through in one document. If you want to store 20 gb of logs, having all of that in one file will make it difficult to go through. 10 2 gb log files is much easier. That’s not so much a consumer issue, but that’s the jist of it.

    • if you assume the second post has ulterior meaning it could be that someone might not know what a crash log is, but most people who have interacted with computers at least once would be at least vaguely familiar window’s file description and understand that text file icon + >200 gb size is not normal

      this is, of course, a rather big assumption.
      most people don’t put that much though in a post and expecting them to will make your online experience a confusing mess.

    •  Liz   ( @Liz@midwest.social ) 
      link
      fedilink
      English
      611 hours ago

      Most people have zero understanding of how programs work. I have slightly more understanding than the average person and I didn’t catch that a crash log would nearly always be a text file.

  • I’ve written code that has generated logs like that. In my case, I had all of my 12 threads writing to a logger, and over the course of 2 hours it got to about 250gb, which was the remainder space on my drive

    •  scops   ( @scops@reddthat.com ) 
      link
      fedilink
      English
      611 hours ago

      Yeah, my OP9 was my third OnePlus phone and my last one. I installed a security update that made the cell radio completely non-functional and had to factory reset it. I use my phone for 2FA to get into my work computer, so this was simply unacceptable.

      I realized I wasn’t doing enough with my phone to warrant flagship prices and ended up switching to a Pixel 6a I got on the cheap. Other than having to add wireless charging with an accessory, I haven’t looked back.

      • I switched to the Pixel 8. It’s okay, good camera but a little buggy. Last phone I REALLY liked was the LG G5 that had a slide-out battery. I think it was t-mobile(?) had a bonus where they gave you a free extra battery and charger for that battery. I could go for a couple days at it’s peak without a charger, just a battery swap