After updating the game I loaded up a game I had going for quite some time, and it ran fine for about thirty minutes, but when I tried to save I was met with this message:
Now, I can reload the last autosave without any problems, but any attempt to save the game causes it to display the message and crash.
This is the last autosave: https://www.dropbox.com/s/17rxl783wotmx ... osave1.zip
Actually this seems to be the problem with all my saves from before the update. New games don't produce this problem though. While, shamefully I'd admit, the saves have over 90 hours invested in them, this problem seems only to have surfaced immediately after the update so I suspect that it might be related to the update specifically.
In my case bad allocation happens when I put a lot of connected roboports without electricity. It seems that it happens during one of those checks when newly created deelectrified roboport looses coverage and connections.
My experiment was:
1. Create 4 roboports at max conenctable (supply) distance from each other and my main roboport network without sypplying electricity. Wait a bit. Crash.
2. Create 4 roboports at max conenctable (supply) distance from each other and my main roboport network supplying each of tehm with electricity right after I put it. Wait a bit. No crash. Continue enjoying the game =)
Yeah and it has nothing to do with "saves" in my case because autosaves are disabled.
So I have been trying to reproduce, and after some time I found out, this happens only on 32bit version (that I use rarely), it is probably caused by the memory addressable space limitation on the 32 bit system.
This causes problem when saving/loading as we changed for new version to first save/load all the map to/from memory in one big block.
We will change the algorithm, to use smaller blocks, but it will probably not happen in 0.10.1, but in 0.10.2
P.S. Let me know if I'm wrong and this happens in 64bit binary as well.
The one I posted does not involves save/load at all.
As I have said autosave is disbaled and direct save/load cause no issue. What causes an issue resides somwhere in an algorithm that recalculates coverage zone of roboports or something closely related to it.