701
efficient game design rule
(lemmy.blahaj.zone)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Sep 2024
701 points (97.7% liked)
196
16243 readers
1908 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
That can happen with any program, and should be a simple fix on the dev side
It is also something that can happen easily. Just program to log an error and then the error happens unexpected every frame.
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.