[0.11.8] Crash on autosave

[sillyfly]

I have played this save for quite a while (17 + hours ), but now it crashes whenever it tries to autosave, and I get this in the log:

Code: Select all

243419.206611  Error Main.cpp:37: Segmentation fault!
./factorio[0x486669]
./factorio[0x59a9a8]
/lib/x86_64-linux-gnu/libc.so.6(+0x35180)[0x7f7523b73180]
./factorio[0x494d54]
./factorio[0x685184]
./factorio[0x81206d]
./factorio[0x8da473]
./factorio[0x94fb1c]
./factorio[0x8a7c08]
./factorio[0xbec9ca]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7f75258060a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7523c23ccd]

Here is the file (11.3 MB):
http://www.filedropper.com/cant-save

I apologize if this is the same as one of the crash reports that have already been fixed, but I couldn't find one with the same symptoms (crash only on autosave, no crash on load, exact error message, etc.)

[sillyfly]

Followup: Just to make sure, I have loaded the previous autosave (2 minutes before this one), and indeed, the first autosave goes flawlessly, then the second one crashes the game. This happens even if I do nothing from loading the game, so it is definitely not the same as the other (power-pole related) crashes.
If needed I can provide the previous autosave as well.

[psihius]

We also had the same issue, playing 3 people. Our save is not small, but from the evidence we see, it looks like that there is a lot of lag from biter pathfinding, that lags the game a lot and autosave in the end just lags so much that game either crashes or everyone gets disconnected.
We play in EU region, so our pings are under 85ms, our network setting is at 99 ms. We also do not play through Evolve/Hamachi - I have set up direct access to my game, so there is no intermediate software involved that can affect the networking. MY connection is 100/100 Mbits, people downloading map from me at speeds of 3 to 6 MBits/sec, pings look rock solid with no or negligible packet loss, ping jittering is rare and usually they stay in +-2-3 ms range.

My specs are:
Running 64 bit 0.11.8 Factorio
Win 7 x64 bit
Intel Q6600 at 3.2 GHz (I admit, not the fastest, but the save is able to run at 60 FPS for me when there are no issues, it just deteriorates into absolute lagfest (like 1-2 FPS a second and after a minute or so can run at 60 FPS again) and then may recover as if nothing happened, one time game runned smoothly when we killed all near by biters and we had almost no polution affecting them.
4GB RAM
SSD (Samsung Pro 256GB, so a fast one with 00GB of free space and 56GB of reserved space for internal stuff)
GeForce 560 Ti (MSI Twin Frorz II)

I set the rendering options to low, but that didn't give any effect, I can run game at max quality with ease.

So, here is the save and last 2 log files with crash/freeze of the game, after which we just went to sleep: https://www.wuala.com/psih/Factorio%20c ... z9xAbBUVlr

The data from Windows event log

Log Name: Application
Source: Application Error
Date: 2015.01.02. 22:04:11
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: psihius-PC
Description:
Faulting application name: Factorio.exe, version: 0.0.0.0, time stamp: 0x54984855
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0x1498
Faulting application start time: 0x01d026bec20d5e82
Faulting application path: C:\Program Files\Factorio\bin\x64\Factorio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8411bb60-92ba-11e4-b067-001e8c533f5a
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-02T20:04:11.000000000Z" />
<EventRecordID>89707</EventRecordID>
<Channel>Application</Channel>
<Computer>psihius-PC</Computer>
<Security />
</System>
<EventData>
<Data>Factorio.exe</Data>
<Data>0.0.0.0</Data>
<Data>54984855</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.18247</Data>
<Data>521eaf24</Data>
<Data>c0000374</Data>
<Data>00000000000c4102</Data>
<Data>1498</Data>
<Data>01d026bec20d5e82</Data>
<Data>C:\Program Files\Factorio\bin\x64\Factorio.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>8411bb60-92ba-11e4-b067-001e8c533f5a</Data>
</EventData>
</Event>

[kovarex]

Thanks for the report, it helped me to fix the problem for 0.11.9.

[sillyfly]

Thanks for the report, it helped me to fix the problem for 0.11.9.

Thanks!
Will I be able to play my save, or is it corrupted?
(I guess I could just wait until 0.11.9 is release and see for myself, but if it is indeed lost I would probably start a new one )

[kovarex]

Thanks for the report, it helped me to fix the problem for 0.11.9.

Thanks!
Will I be able to play my save, or is it corrupted?
(I guess I could just wait until 0.11.9 is release and see for myself, but if it is indeed lost I would probably start a new one )

The save worked properly for me, so it will probably work properly for you as well in 0.11.9

[sillyfly]

Just got a very similar crash:

Code: Select all

./factorio[0x4886c9]
./factorio[0x59fce8]
/lib/x86_64-linux-gnu/libc.so.6(+0x35180)[0x7f4422b97180]
./factorio[0x9e995c]
./factorio[0x9e983d]
./factorio[0x9eb174]
./factorio[0x9a564e]
./factorio[0x9a5fe5]
./factorio[0x9a6092]
./factorio[0x825999]
./factorio[0x967fab]
./factorio[0x96a7ff]
./factorio[0x44136e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4422b83b45]
./factorio[0x442a71]

Sadly, I didn't have the autosave on, so I can't get give a save.
Thinking about it, it also means this crash could not be related to autosave. But the log does look similar.
Anyway, if I get it again I will open a new report with a save file.

Edit: I realize now I forgot to mention - this new crash is in 0.11.9, not 0.11.8

[cube]

Just got a very similar crash:

Code: Select all

./factorio[0x4886c9]
./factorio[0x59fce8]
/lib/x86_64-linux-gnu/libc.so.6(+0x35180)[0x7f4422b97180]
./factorio[0x9e995c]
./factorio[0x9e983d]
./factorio[0x9eb174]
./factorio[0x9a564e]
./factorio[0x9a5fe5]
./factorio[0x9a6092]
./factorio[0x825999]
./factorio[0x967fab]
./factorio[0x96a7ff]
./factorio[0x44136e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4422b83b45]
./factorio[0x442a71]

Sadly, I didn't have the autosave on, so I can't get give a save.
Thinking about it, it also means this crash could not be related to autosave. But the log does look similar.
Anyway, if I get it again I will open a new report with a save file.

Edit: I realize now I forgot to mention - this new crash is in 0.11.9, not 0.11.8

This is a different bug and it is fixed now as well

[sillyfly]

Nice to now
It is amazing how you can fix a bug when I can't even say how it happened.