Page 1 of 1

[Dominik][0.17.79] Crash loading a 0.16 Seablock save (FluidManager::moveOut)

Posted: Sun Dec 01, 2019 4:54 pm
by DorianTheFactorian
I decided the start playing a 0.16 Seablock save file. I downloaded the new seablock config modpack and a few extras. When I attempt to open the save file, the green progress bar over the menu screen completes, and then I'm given a macOS popup saying the game crashed. What's peculiar is that I have another save from the same map (~20 hours previous, not much in Seablock time) that loads in 0.17.79 as expected.

Attachments:
* factorio-current.log
* seablock-exper-016.zip (causes crash)
* seablock_016.zip (loads okay)

Link to save files on Google Drive: https://drive.google.com/drive/folders/ ... sp=sharing

Re: [0.17.79] Crash loading a 0.16 Seablock save

Posted: Thu Dec 05, 2019 11:06 pm
by TruePikachu
That log does not contain any crash.

Re: [0.17.79] Crash loading a 0.16 Seablock save

Posted: Mon Dec 16, 2019 8:24 pm
by boskid
Yes!, crashed for me.

Code: Select all

c:\cygwin64\tmp\factorio-build-shnskz\src\fluid\fluidmanager.cpp (309): FluidManager::moveOut
c:\cygwin64\tmp\factorio-build-shnskz\src\fluid\fluidboxmanager.cpp (567): FluidBoxManager::onDestroy
c:\cygwin64\tmp\factorio-build-shnskz\src\fluid\fluidboxmanager.cpp (594): FluidBoxManager::reset
c:\cygwin64\tmp\factorio-build-shnskz\src\entity\assemblingmachine.cpp (831): AssemblingMachine::reset
c:\cygwin64\tmp\factorio-build-shnskz\src\entity\assemblingmachine.cpp (430): AssemblingMachine::setupForCrafting
c:\cygwin64\tmp\factorio-build-shnskz\src\entity\assemblingmachine.cpp (986): AssemblingMachine::setup
c:\cygwin64\tmp\factorio-build-shnskz\src\map\map.cpp (867): Map::setupEntities
c:\cygwin64\tmp\factorio-build-shnskz\src\scenario\scenario.cpp (307): Scenario::loadFactory
c:\cygwin64\tmp\factorio-build-shnskz\src\scenario\parallelscenarioloader.cpp (151): ParallelScenarioLoader::doLoad

Re: [Dominik][0.17.79] Crash loading a 0.16 Seablock save (FluidManager::moveOut)

Posted: Fri Jan 10, 2020 4:03 am
by Rseding91
This should be fixed for the next release.