This might be the underlying problem here. Since I'm running Ubuntu I can't really tell for certain, but I know we have had similar bug reports in the past. I tested a bit more with the attached savegame, set autosave to each minute and let it run for a while. No crashes, though I saw that the process exceeded 2.0 GiB after a short while.
Could someone running Windows please check whether they can reproduce this issue?
>The game window disappears and the Windows Desktop is shown. No error message is displayed.
Could you check for a file called stderr.txt in the folder where Widelands is installed (at least I believe that's where it is stored)? Note that it is overwritten each time you start Widelands, but it might log some error message there. Otherwise, WL might print some error if you start it in a terminal (just open cmd and run widelands.exe).
> Looks like the Process is near the 2GB limit.
This might be the underlying problem here. Since I'm running Ubuntu I can't really tell for certain, but I know we have had similar bug reports in the past. I tested a bit more with the attached savegame, set autosave to each minute and let it run for a while. No crashes, though I saw that the process exceeded 2.0 GiB after a short while.
Could someone running Windows please check whether they can reproduce this issue?
>The game window disappears and the Windows Desktop is shown. No error message is displayed.
Could you check for a file called stderr.txt in the folder where Widelands is installed (at least I believe that's where it is stored)? Note that it is overwritten each time you start Widelands, but it might log some error message there. Otherwise, WL might print some error if you start it in a terminal (just open cmd and run widelands.exe).