this post was submitted on 19 Sep 2024

745 points (97.8% liked)

196

16579 readers

1679 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago

MODERATORS

moss@lemmy.blahaj.zone

greembow@lemmy.blahaj.zone

moss@lemmy.world

queue@beehaw.org

funky_rodent@lemmy.blahaj.zone

PeachyMcPeachface@lemmy.blahaj.zone

greembow@lemmy.world

remotelove@lemmy.ca

Roflmasterbigpimp@feddit.de

qaz@lemmy.world

A_Very_Big_Fan@lemm.ee

qaz@lemmy.blahaj.zone

A_Very_Big_Fan@lemmy.world

qaz@lemmy.dbzer0.com

qaz@sh.itjust.works

qaz@lemmy.sdf.org

745

efficient game design rule (lemmy.blahaj.zone)

submitted 2 months ago by nicknonya@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone

47 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] dustyData@lemmy.world 37 points 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.