Player.log is a whopping 48.4 GBs

[Kirbubble2]

I checked my SSD b/c I wasn't able to save my game anymore. It turns out that the text file named "Player.log" is a whopping 48.4 GBs. It is located under C:\Users\kirby\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios

Can I delete it? Or what can I do to solve this space hog? B/c it doesn't seem normal.

[Qiox]

My Player.log is 5 Kb in size and the creation date coincides with when my play session started earlier this evening.

There's also a Player-prev.log file which is 14 Kb in size and it as created this afternoon when I started an earlier session.

Looks like it should be creating a new one every time you play and keeping 1 backup.

Did you start playing 2 years ago and never shut down the program?

[brian_va]

not everyone will get it, but its not uncommon. i seem to remember this is an underlying issue with the unity engine (from other games) but only about 85% on that. you can delete, shouldn't cause a problem.

[Bozobub]

This has been a problem with a few mods, at times. I believe you can accidentally turn on persistent logging n the console, as well, but that seems unlikely here.

[Razor 2.3]

Something in the game is spamming the log.

If the game freezes when you try to quit, it's probably due to too many sounds trying to play at once at some point. The game freezes when you quit, and proceeds to write the same error to the log as fast as it can until you terminate the program some other way. It's a bug in the game that will never get fixed because it tends to happen only while playing with mods.

If not, one of the mods is writing way too much to the log. If you could open it, you might get an idea of what's going on, but good luck with that.

[Jigain]

Yeah, it's a known issue that some mods will cause the player.log file to bloat to sizes of several hundred gigabytes. The game itself does not write that big log files, so it's absolutely, 100% a mod issue.

And yes, it's just a log file, you can delete it.

[TwoTonGamer]

I'll second Jigain in that it is a mod that is doing this.
I've read similar posts many times over the years. A mod author has forgotten to turn off some debug log option and it bloats and bloats the more you play.

It is different mods each time, so I can't suggest a solution better than visiting mod pages for reports of player.log bloat.

[Saint]

lol glad I found this thread. mine was up to 57 gigs.

[derSandman]

that's nothing at all .. my "PlayerLog" had 170GB! My System suddenly crashed because drive C suddenly had 0 MB free.
For me, nothing was going anymore. And disk analysis says nothing about the log file or what eats the memory. It just says "other files". In explorer, it does not even display this data size. I almost went crazy ... the program "TreeSize Free" showed me that I was spamming with logs.