Game crashes just after auto-save sequence

[kano]

What happened:

The game autosaved in commitment mode, and then just shut down.

What I expected to happen:

Game continuing just as before.

Log file in the attachment.

Mod List:

Code Select Expand

Harmony
Core
HugsLib
Moody
Expanded Roofing
Miscellaneous 'CORE'
Misc. Robots
Rimsenal: Core
Rimsenal: Enhanced Vanilla
Rimsenal: Feral Faction
Rimsenal: Security Pack
Snap Out!
Hotkeys
Children, school and learning
A Rimworld of Magic
JecsTools
Expanded Prosthetics and Organ Engineering
Rah's Bionics and Surgery Expansion
Follow Me
Colony Manager
Hospitality
Humanoid Alien Races 2.0
Mod Manager
Dubs Bad Hygiene
Recipe icons
DontBlockDoor[1.0-1.2]
Wall Light
Misc. Robots++
Medical Tab
Work Tab
Animal Tab
Relations Tab
Blueprints
Giddy-up! Core
Giddy-up! Battle Mounts
Giddy-up! Caravan
Giddy-up! Ride and Roll
Replace Stuff
Increased Stack
Android tiers
Rimsenal - Rimhair
EdB Prepare Carefully
Where is my weapon?
Genetic Rim
Realistic Rooms
Interaction Bubbles
Allow Tool
Animals Logic
Dubs Mint Menus
More Sculpture
[T] MoreFloors
Empire
Long Distance


Save file: https://filetransfer.io/data-package/EKK6jUNS#link

What I've done already:

Tried removing the Medical System Expansion, no avail: same error (Verse.DamageWorker_AddInjury:FinalizeAndAddInjury)
Tried removing Rimsenal entirely, no use.
Tried removing JecsTools and Rimworld of Magic, redone the save and the characters only to vanilla aspects using EDB, no use as well: same error.

[Canute]

Hi,
the logfile you attached don't include any safegame loading, so there there couldn't be any error from saving.
So i think you add the wrong logfile or you started Rimworld before so the logfile with the error got overwritten.
What is "commitment mode" is that some linux thing, because i think you use linux ?

You should try at first to create a new colony without mods (harmony,hugslib,jecstools,alienraces are ok) and check if anything works fine.
So you can exclude that is something wrong with your installation or your OS made problems.

[kano]

Commitment mode is something related to the save game, in which you can only save when you quit or autosaving. It is contrary to "reload anytime" mode. I do use Linux but this game option is unrelated to OS.

So, I did not find any other logs; I've reinstalled the game and the modpack and I'll try again to play the game, this time running from console so I can check if it drops any more queues.

Edit: the savegame I have loads just after the auto-save sequence, so I don't have the complete log on that. After 10-15 seconds, the game crashes.

[Canute]

Did you mean with "Commitment mode" the permadeath mode ?

Rimworld creates a logfile (player.log) everytime you start it. And the old logfile get renamed (Player-prev.log).
At last at windows but i think ludeon unify that for all OS versions.

When rimworld crash by itself, you will get a crash window and a crash folder will generated. But this isn't in your case.
But it still can happen that a mod could crash rimworld, or a mod doing some bad thing so the OS quit the process.

But without log, noone can say anything about it.

You can try if the problem happen on a new colony too. Enable developer mode at the option, then you can quickstart a new test colony with the top right icon (if you got hugslib installed).
When you got the same problem at new colonies, you can disable mods, until the problem disappear and you could identify the bad mod.

[kano]

Apparently, something happened while the game updated.

Left it since 1.0, and never played since. Now on 1.2, maybe the updates from 1.1 to 1.2 corrupted some mod files and consequently made the game act weird.

I reinstalled the game and the entire modpack and 7 days now, working completely fine. The crash was happening when one of the pawns were being damaged, and now damage is just fine.

Thanks for the support, anyways.