Game crash when finishing a level

  • updated
  • Pending Customer

OS: Win 10 1903 (64bits)

CPU: AMD 3850 fx

RAM: 16 Go

VRAM: 8 Go on SSD

GPU: GTX 1060

Game version: 2.0.7f1

Hello, i've been able to consistently have the same issue: i can play the WTFO, choose campaign and all, but at the end, when i win or loose, the game save what i have done, the achievement and all, then crash to desktop with the message of the crash dump

The only things i noticed is that the game do not crash when i was doing some of the speedrun achievements under 35 minutes, so i was wondering if it would be a memory leak or something amongs these lines, but i do not have the same troubles with other unity games

War For The Overworld crashlogs.7z

Game Version:
Steam Public
Lee "Noontide" Moon
  • Pending Customer

Hi Dracus,

Sorry to hear you're having problems with the game crashing at the end of levels and apologies for the delay in getting back to you over the holiday season. We've reviewed the crash logs you sent over and each one consistently shows the game is unable to allocate further memory on your machine, causing the crash.

This seems pretty peculiar given that your system has 16GB of RAM installed. But upon inspection of the allocations for WFTO we're only using a few GB of this at the time of the crashes. Further evaluating your logs could indicates one of two possibilities:

  • Your Paging File is running out of memory and thus the game is not able to allocate to that.
  • For whatever reason, you're running out of physical memory and the game is not able to allocate directly there.

In either case, there are no indications that there is a problem on our side.

Initially, I would suggest the following:

  1. Trying switching off all unnecessary programs while running WFTO to free up as much space as possible.
  2. Expand your paging file's maximum allocation size. This may be too low to allow further allocations with other applications taking up space.
  3. As a hail mary, you could try disabling the paging file altogether, though this may result in undesirable side effects. It should be easy enough to re-enable in any case.

Hope this helps,