1.19n oom after reloads
Had a slowdown and finally oom after 2 reloads. I haven't been getting any other oom's. Great work!
http://dl.dropbox.com/u/16872572/n%20oomslowdown%20after%202%20reloads.zip
Had a slowdown and finally oom after 2 reloads. I haven't been getting any other oom's. Great work!
http://dl.dropbox.com/u/16872572/n%20oomslowdown%20after%202%20reloads.zip
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:
What AlLan said.
Just to clarify my thoughts on the matter (from playing, testing, and reading various dev posts):
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.
It was a reload from within a game. There was a time where you got an instant crash from 1 reload so they have made some improvement. I agree, this isn't as big an issue as the other oom's.
Egad, instant crash from a reload... not good.
Welcome Guest! Please take the time to register with us.