1.19 Out of memory crash

Played game a bit, till turn 50 or so. Out of memory error message then crash.

debug.err here.

No dump got created.

 

 

Funny thing, hadn't an out of memory error in 1.11 in a long time. :P

 

Edit:

  1. Debug Message:  - Ending Turn 50 -
  2. Debug Message:  Current Memory Usage: 1212820 KB

That's what I call a memory leak. :p

9,488 views 13 replies
Reply #1 Top

Wow! Something happened. Something came in and scooped up 500 megs in 1 turn.

Reply #2 Top

Vandenburg,

It appears to have crashed while auto-saving.  Would you happen to still have the previous auto-save before that?

If so, please email it to codecritter@stardock.com.  It may help us to identify what was using so much memory there.

If you don't have the save, that's ok.  If it happens again, please let us know and send the previous auto save and auto save files.

In the meantime, we'll take a look through the debug.err and see what we can find.

Thank you.

Reply #3 Top

I'm getting the same crash. I e-mailed the logs.zip file created by your sdsupporttool.exe file to support@stardock,com, as that drop.io service is pining for the fjords. If this tool doesn't generate the info you need, could you inform us of a better way to get the appropriate info to the right people?

Reply #4 Top

Ah, sadly I don't have the autosave anymore. Had to play more Elemental. ;)

But will keep a look out for it.

Reply #5 Top

 

  Vandenburg what mods were you running when this happened?

Reply #6 Top

Quoting Derek, reply 5
 

  Vandenburg what mods were you running when this happened?
End of Derek's quote

None. :)

Reply #7 Top

I'm also getting this crash never had an out of memory error in any previous version getting it regularly now and I'm running Windows 7 64bit with 4Gb. But the program is still 32 bit of course so it can't access all that ram. I'll save and post it the next time it happens.

I would add this is in new games under this version with no mods.

Reply #8 Top

Just had it happen again, much later in the game. Seems to be connected to saving.

DebugMessage:  SAVE GAME: Saving Quick Data
DebugMessage:  SAVE GAME: Saving Quick Data - Complete
DebugMessage:  SAVE GAME: Saving World
DebugMessage:  Error allocating memory: 19922944 bytes.

Here is the whole debug.err file.

 

And here are the 2 autosaves.

 

Should I also send them per mail?

Reply #9 Top

And it happened again.

DebugMessage:  SAVE GAME: Saving XML Data (start)
DebugMessage:  SAVE GAME: Saving XML Data (end)
DebugMessage:  SAVE GAME: Saving Quick Data
DebugMessage:  SAVE GAME: Saving Quick Data - Complete
DebugMessage:  SAVE GAME: Saving World
DebugMessage:  Error allocating memory: 14680064 bytes.

Another debug.err file.

And again, failed to secure the autosaves before I overwrote them. :p

Reply #10 Top

Debug Message:  - Ending Turn 195 -
Debug Message:  Current Memory Usage: 1263016 KB
Debug Message:  Cities in World: 14
Debug Message:  Units in World: 319
Debug Message:  GarabageCollection - Begin
Debug Message:  GarbageCollection - Complete
DebugMessage:  Updating ZOC.
DebugMessage:  About to auto save.
DebugMessage:  Deleting save game.
DebugMessage:  SAVE GAME: Saving XML Data (start)
DebugMessage:  Error allocating memory: 13631488 bytes.

You know the deal. ;)

debug.err

savegames

Reply #11 Top

I am now getting the same OOM lock up on saving the game that I did with 1.19 that I did with the previous version.    It just takes a number of turns before the problem shows up.    It looks like the memory fix in 1.19 did not take care of every OOM problem.

Reply #12 Top

I also had an OOM crash when trying to quicksave. I'd been playing for 6 hours so I thought it was fair enough. :)

Reply #13 Top

Once I get well into the game, it's doomed. The memory leak takes over and kills it every 20-40 minutes. I've emailed in some debug and saves for your perusal.