Hi mywhiskey,

Were these oom's from loading a game from within a game? Or were they reloading after a fresh instance of Elemental? It appears reloading a game from within a game around 5-6 times will inevitable always lead to an oom (looks like garbage collection process leaves 40-50MB if garbage laying around per game). Just curious. Thanks.

[Edit] You could test this by doing the following:

1. Start new instance of Elemental
2. Load last saved game
3. Do nothing - go back to main menu and load your last saved game again
4. Rinse and repeat until OOM - the game appears to leave about 40-50mb of garbage left over from prior game and it will oom usually within 5-6 turns I think

Just to clarify my thoughts on the matter (from playing, testing, and reading various dev posts):

1. Definitive oom's from loading a game from within a game due to garbage collection process not clearing crud from the prior game (I'm not a programmer, just read up on memory leaks and such a couple of weeks ago)
2. Random oom's from bugs and normal playing

I think 1 is on the backburner for post 1.2 and possible revamp of how the game handles memory. 2 is what SD is focusing on as urgent for this beta series. I understand this plan of attack. The problem is that anyone who does 1 in any fashion (does it once, twice, etc) increases the chance of a 2.

In short, to eliminate 1 as a variable, I always start a fresh game of Elemental when loading a game. Not ideal, and not as designed, but a reality we're in at the moment. I have faith the SD crew will get 1 resolved eventually - the engine needs to be stable not only for EWOM enjoyment, but for FE. I can't wait to put the stability issues behind us so both the SD crew and the entire mod community can focus solely on new content. It's going to be exciting content-wise once all cylinders are firing.

Egad, instant crash from a reload... not good.