Factorio 0.14.21
This is probably related to one of the many mods in some way, but a hard crash with no feedback is arguably a bug in the mod container anyway.
I opened debug in VS2015 for fun, and still have it open for now at the crash/breakpoint and can see parts of the internal state (although obviously no source to reference for it except call stack) so if anyone knows which parts could be useful let me know within ~12hrs and I'll add it in a reply.
The crash occurred once the world loading bar was completely full and sat there for a 5~10 seconds, after copying the entire factorio folder (so as not to collide with VS debug and running/crashed instance) The game loaded and migrated without problems.
I can also upload world+mods if needed, I do still have a copy of the pre-migration world although I don't have all the previous mod versions on hand as they were automatically updated. Also a few of the mods have been tweaked locally (small changes but probably relevant if trying to reproduce elsewhere, the modified mods were not updated during this anyway).
Crash on loading world (after updating mods, not repeatable)
Crash on loading world (after updating mods, not repeatable)
- Attachments
-
- Presumably this is what it was trying to do when it crashed
- Second try migrations.PNG (166.54 KiB) Viewed 1456 times
-
- VS2015 Call Stack.PNG (19.33 KiB) Viewed 1456 times
-
- factorio-previous.log
- contains mod updates+restart
- (26.67 KiB) Downloaded 84 times
-
- factorio-current.log
- (24.87 KiB) Downloaded 73 times
Re: Crash on loading world (after updating mods, not repeatable)
The crash log doesn't show anything useful (no stack trace generated) and the line you showed in the debugger doesn't show anything either.
Without some way to reproduce the issue there's nothing I can do.
Without some way to reproduce the issue there's nothing I can do.
If you want to get ahold of me I'm almost always on Discord.
Re: Crash on loading world (after updating mods, not repeatable)
Ok that was weird. There might not be a bug at all, or maybe just a missing catch for a rare obscure exception. I hit continue in VS after your reply and the game continued on to load and migrate normally. There was however something odd that happened at least as Windows created a prompt about an exception thrown somewhere with the option to debug which is why I opened VS in the first place.