[0.17.4] [Linux] corrupted size vs. prev_size on first start

[Ayamari]

I downloaded and extracted the full 0.17.4 tarball, copied over my config and saves into the new structure, then tried to start the game.
The first time I tried to start the game I got the following error:

Code: Select all

   0.000 2019-03-02 06:58:24; Factorio 0.17.4 (build 43174, linux64, alpha)
   0.035 Operating system: Linux (Ubuntu 18.04)
   0.035 Program arguments: "./bin/x64/factorio" 
   0.035 Read data path: /opt/factorio/data
   0.035 Write data path: /opt/factorio [156410/226263MB]
   0.035 Binaries path: /opt/factorio/bin
   0.042 System info: [CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, 8 cores, RAM: 32095 MB]
   0.042 Environment: DISPLAY=:1, WAYLAND_DISPLAY=<unset>
   0.042 Display options: [FullScreen: 0] [VSync: 1] [UIScale: automatic (100.0%)] [MultiSampling: OFF] [Screen: 255] [Lang: en]
   0.128 Available displays: 2
   0.128  [0]: Dell S2716DG 27" - {[0,0], 2560x1440, SDL_PIXELFORMAT_RGB888, 120Hz}
   0.128  [1]: Dell S2716DG 27" - {[2560,0], 2560x1440, SDL_PIXELFORMAT_RGB888, 120Hz}
   0.225 Initialised OpenGL:[0] GeForce GTX 1070/PCIe/SSE2; driver: 3.3.0 NVIDIA 390.77
   0.225   [Extensions] s3tc:yes; KHR_debug:yes; ARB_clear_texture:yes, ARB_copy_image:yes
   0.225   [Version] 3.3
   0.250 Graphics settings preset: very-high
   0.250   Dedicated video memory size 8192 MB
   0.250 Graphics options: [Graphics quality: high] [Video memory usage: all] [Light scale: 25%] [DXT: high-quality]
   0.250                   [Max load threads: 32] [Max texture size: 0] [Tex.Stream.: 0] [Low quality rotation: 0]
   0.309 Loading mod core 0.0.0 (data.lua)
   0.359 Loading mod base 0.17.4 (data.lua)
   0.505 Loading mod base 0.17.4 (data-updates.lua)
   0.577 Checksum for core: 3928040144
   0.577 Checksum of base: 60305742
corrupted size vs. prev_size

All consecutive attempts work just fine.

[Loewchen]

Did you move over settings from a 0.16 installation?

[Ayamari]

No, the settings were from a previous 0.17.2 install.

[Rseding91]

Does this still happen for you?

Since it's a linux/mac specific error there's nothing I can do to work on it from my end. A quick google search suggests maybe dynamic linked libraries on your end may be linking to the wrong versions which could produce this error. But, that's outside of what we control so if that's the case there's nothing we can do.

[Ayamari]

I am sorry for resurrecting this, but I only now noticed it's still as "Pending".
Turned out that PC had bad RAM and I replaced it a few years ago. I no longer have access to it, and haven't seen anything like this in the last few years either.