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