[0.9.8 & 0.10.1][kovarex] Game crashes instantly

[Fact_3011]

When I try to load my last savegame factorio crashes instantly. This Windows message says as usual nearly nothing: stopped working, APPCRASH, some useless numbers etc. The same issue with this save on 0.9.8 and the new 0.10.1 release. I use the 64Bit versions without installation and no mods. Older saves and the autosaves are still working. Probably there is same state with causes this bug during loaging or saving. I dont know, if the savegame is already broken(saved in 0.9.8) or the issue is completly caused through loading the game. I am using Windows 8.1 x64.
Because of the autosave it is not a big trouble for me. But in other cases it could be really bad.

The save: (Too big to upload directly?)
http://www.imagenetz.de/download,file=9 ... 210dddff02

[kovarex]

Hmm, the save is broken, and I don't see an easy way to diagnose it.

Do you have some other autosaves before this became unloadable?

[Fact_3011]

They are overwritten. But I have once before it appeared and a save some times after the broken once. I have not done very much between the broken save and this one. But it seams, that some time elapsed because for example the dead bitters are disappeared already. In the save before I haven't started attacking yet. I can upload these, but I am pretty sure that it wont help. They work perfectly. I can save and reload as often as I want and there are no crashes. So I think the problem causes by a short "special situation". Perhaps it has something to do with these capsules. I never used these before. However, should I upload a savegame nevertheless?

[kovarex]

It is worth a try.

So you did not create blueprints or manipulate them before it happened?

[Fact_3011]

No. Of course, I used some blueprints many saves before by attacking some other (much bigger) native spawner towns for fast wide spread tower and wall placement. But I wanted to try this newly researched capsules as mentioned. At the moment there should be not even a docking station on the map for a while. No blueprints inside the inventory.

Ok. The saves...
Before: http://www.imagenetz.de/download,file=c ... 6e064391fa
After: http://www.imagenetz.de/download,file=5 ... 914368ea35

[Fact_3011]

I have a similar problem again. I'm unsure, if it is related with the previous problem. Same situation but some other messages. I load a save in a combat. In 0.10.1 the game crashes with this windows error "BEX64". In 0.9.8 there is an windows message box witch says "bad allocation". Then the game closes immediately. Every savegame with this problems shows this behavior in 0.9.8 and 0.10.1. And the defect savegames can occur in 0.9.8 and 0.10.1. I have tested it. When I try to fight this spawner area, about every second time the savegames will be damaged. This can happen to autosaves and normal saves. Because it is reproducible this time, it becomes a little bit annoying now. Am I doing something wrong? Possibly other people can not reproduce it as easy as I can. But I have already 4 defect saves or so. Hopefully enough for further analysis. 16GB of RAM are in my computer.

Before crash. It is working so far: http://www.imagenetz.de/download,file=d ... bbb604c801
Crashed: http://www.imagenetz.de/download,file=4 ... 94f786cf86

EDIT:
It is more frequent than every second try.

[kovarex]

Thank you for the saves, it helped me to identify and fix the bug!

The bug was, that the game was saved wrongly when:
There was a player with follower robots active. The player had to be in a car, and the car had to have blueprints in the trunk, and these blueprints had to have a roboport in it

Fixed for 0.10.2 (To be released today).

[sillyfly]

Thank you for the saves, it helped me to identify and fix the bug!

The bug was, that the game was saved wrongly when:
There was a player with follower robots active. The player had to be in a car, and the car had to have blueprints in the trunk, and these blueprints had to have a roboport in it

Fixed for 0.10.2 (To be released today).

Wow. That's very specific!
I kinda wonder how this came to be a problem

Sounds a bit like those old-school quest games

[kovarex]

Well, yes, this scenario is specific to squeeze the error from the mistake we make in one of our saving mechanisms, we were trying to be too smart there