Playing the crucible I noticed the RAM is filling up
First of all I like War For The Overworld very much, I played it a lot. Like I loved and played Dungeon Keeper in the past.
On one map in the crucible, I mostly end up number one, Memento Moor
But I have a big issue since patch 2.0.2 with the crucible (not tested anything else)
Playing the crucible I noticed the RAM is filling up with more than 1MB per second. ( I don’t know if it did this before, but it not a normal behaviour)
This (I think) ending up crashing the game (program will not respond).
- At wave 55, 2,694,174 point. The game did crash.
- I ended (finished) up in wave 170, 7,184,542 point. But the game did not go to the score board. It did crash! ( but it managed to get my score to the score board after all, 1st place and not playing seriously because of a expecting crash)
I played the crucible a lot, and in the end my computer will stutter and slow down a higher waves (like 199>), but it never give up one me until now. It has to be patch 2.0.1 or 2.0.2. Playing a game in fear of a crash is a no go!
Now, how to solve this problem? Patch 2.03?
Today I played a Crucible game of 2,5 hours in Memento Moor. I ended (finished) up in wave 174, 7,836,578 point. But the game did not go to the score board again. It did crash! But it managed again to get my score to the score board after all, 1st place. I had broken down defences to end the game because of the expecting crash. I watched the RAM filling up, it looks like the virtual RAM is filling up to during the game
After one hour playing the RAM is filling up faster
I have 16GB of RAM (14,2GB is left for the game) and its full after 2 hours of playing, then the real problems start to occur.
I was thinking, when I reserve 64 GB of virtual RAM on my SSD, I can play without crash. I will not run low on memory
But on wave 195, with 26,205,842 points and with 2:55:43 play time the game freezes! I waited more than 5 minutes with hope the game would continue… and it did. But my mood and the gameplay was destroyed. I let the game end and did little to get a better score.
Wave 220, with 34,002,951 points and with 3:01:37 play time the game was over but it did not go to the end screen, it crash again. Or should I say freezes again. I waited more than 10 minutes to respond, but I had to end it by force. I even could not get into the windows task manager were I watch the RAM usage. It could see I the end the memory usage was 100>#/span###
But it managed again to get my score to the score board after all, 1st place
This gameplay with freezes and crashes is just not right, it’s not a good experience, I end up 1st place but I want a fair game, if other player with 8GB have this problem they never get big scores.
Well now I am don trying, could someone help me with this problem, dev’s?
This time I played I the RAM filling up. I noticed when the game is on pause Press Esc, the menu), the RAM is still filling up. I left the game for a while on pause, later I ended the game and wanted to go to the main menu. But here the game crashed. The RAM was not completely filled this time but was filling up
The last crash report was from 25-05-2018 and is outdated, there were no newer reports. I don’t know why, because I played frequently after that date.
And of course in the crucible, no save game.
WFTO version 2.0.2
Windows 10 1803 64 bit
16GB RAM DDR3 2400
Quadcore Intel Core I7-4770K
Nvidia Geforce GTX770
I updated the network drivers, and Graphic drivers. No effect
Update windows to 1803. No effect
Steam verification, 1 issue found (1 file failed to validate and will be reacquired), Fixed. No effect
But I notice when I start the game this 1 issue is returning. Every time! output_log 3-7-18 Only short startup game.txt
Reinstall game. Done, but not tested. But with steam verification, again1 issue found, and fixed
Game crash in ending, not going to scoreboard wave 170 30-6-18
Game crash in ending, not going to scoreboard wave 174 30-6-18
RAM memory in lets say the last half hour 30-6-18
RAM memory in lets say the last half hour 30-6-18 (2)
RAM memory when ending game (By Force) 30-6-18