Game crash on every savegame loading

[Zjadlbymcos]

Yesterday Factorio works fine. Today game crashes after savagame end's loading. I tried to run new campaign but the game crashes too.

Logs and save: https://drive.google.com/drive/folders/ ... 1Z5MGpzUzA

[Loewchen]

Init:

Code: Select all

0.000 2017-06-27 18:47:38; Factorio 0.15.23 (build 30400, linux64, steam)
   0.098 Operating system: Linux (LinuxMint 18.1)
   0.098 Program arguments: "/media/sewo/Dane/.steam/steamapps/common/Factorio/bin/x64/factorio" 
   0.098 Read data path: /media/sewo/Dane/.steam/steamapps/common/Factorio/data
   0.098 Write data path: /home/sewo/.factorio
   0.098 Binaries path: /media/sewo/Dane/.steam/steamapps/common/Factorio/bin
   0.117 System info: [CPU:        Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 4 cores, RAM: 7665MB]
   0.119 Display options: [FullScreen: 0] [VSync: 0] [UIScale: 90.7609%] [MultiSampling: OFF] [Screen: 1]
   0.159 Available display adapters: 2
   0.159  [0]: resolution 1920x1080px at [1920,0]
   0.159  [1]: resolution 1920x1080px at [0,0]
   0.159 Create display on adapter 1. Size 1280x720 at position [310, 162].
   0.218 Initialised OpenGL:[1] Mesa DRI Intel(R) Ivybridge Mobile ; driver: 3.0 Mesa 12.0.6
   0.258 Graphics settings preset: medium
   0.258 Graphics options: [Graphics quality: low] [Video memory usage: all] [Light scale: 25%] [DXT: auto]
   0.463 Loading mod core 0.0.0 (data.lua)
   0.474 Loading mod base 0.15.23 (data.lua)
   0.599 Loading mod base 0.15.23 (data-updates.lua)
   0.654 Checksum for core: 3550962641
   0.654 Checksum of base: 1793295924
   0.917 Info PlayerData.cpp:58: Local player-data.json available, timestamp 1498581084
   0.917 Info PlayerData.cpp:63: Cloud player-data.json available, timestamp 1498341573
   1.083 Initial atlas bitmap size is 2048
   1.087 Created atlas bitmap 2048x2029

End:

Code: Select all

  72.476 Info GameActionHandler.cpp:3305: MapTick (3336013) processed PlayerJoinGame peerID(24) playerIndex(15) mode(create ) 
  72.510 Error CrashHandler.cpp:232: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
  73.396 Warning Logger.cpp:396: Symbols.size() == 15, usedSize == 9
#0  0x0000000000aba39d in Logger::logStacktrace(StackTraceInfo*) at /tmp/factorio-qL5CA3/src/Util/Logger.cpp:421
#1  0x00000000006f0310 in CrashHandler::writeStackTrace() at /tmp/factorio-qL5CA3/src/Util/CrashHandler.cpp:105
#2  0x00000000006f0594 in CrashHandler::SignalHandler(int) at /tmp/factorio-qL5CA3/src/Util/CrashHandler.cpp:237
#3  0x00007f5f4a28e4b0 in ?? at ??:0
#4  0x0000000000ae144e in composeDiffuseAndLight at /tmp/factorio-qL5CA3/src/Graphics/DrawEngine.cpp:174
#5  0x0000000000e68e74 in render at /tmp/factorio-qL5CA3/src/Graphics/DrawEngine.cpp:138
#6  0x0000000000ee1f5b in render at /tmp/factorio-qL5CA3/src/Graphics/GameRenderer.cpp:190
#7  0x00007f5f4a279830 in render at /tmp/factorio-qL5CA3/src/GameView.cpp:936
#8  0x000000000040b269 in render at /tmp/factorio-qL5CA3/src/Game.cpp:330
  74.345 Warning Logger.cpp:396: Symbols.size() == 14, usedSize == 8
  74.345 Error CrashHandler.cpp:106: Map tick at moment of crash: 3336015
  74.345 Error Util.cpp:80: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.

[Rseding91]

Thanks for the report. I can load your save file without any problems and the stack trace is crashing trying to draw something. With both of those things plus you having linux that leads me to believe there's something wrong with either your graphics card, drivers, OS or some combination of those.

Do you have any other computer you can test your save file on? Because there's nothing I can do for you at the moment.

[Zjadlbymcos]

That's my only PC.

Funny thing is that I fixed that issue by removing ~/.factorio/config/config.ini
Maybe "mint update" changed something with my graphics or something I don't know.

Anyway, thank you for quick respond.