[BUG] Memory leak(s)

from Elemental Forums

Have noted a lot of bugs in the beta, ALL of which have been reported.

However, I can add that the game appears to have at least one memory leak. On loading and starting a game memory usage begins a steady slide up to 1GB or more after about an hour of play. At the moment there are enough crash bugs that this isn't such a big problem, but once those are sorted we're going to hit the wall hard and fast on memory usage, IIRC XP32 will crash out at 2GB...

I don't have much in the way of useful diagnostic critera or data I'm afraid, just that it's reproducible 100% of the time if you can keep the game running long enough, so it should be pretty easy to find with some diagnostics tools.

4,448 views 3 replies
Reply #1 from Elemental Forums Top
The "debug.err" files I have sent them include lots of what looks to me lke references to memory leaks. I *think* by now they have mountains of evidence to help them track them down. Here's the last several lines of my current file, presumably written just before it crashed. DebugMessage: Not all memory has been freed from memory system AStar. DebugMessage: 37908 bytes of memory still allocated. DebugMessage: Unallocated Mem: 129 bytes of memory from line 218 of F:\Projects\Kumquat3D\Source\parse.cpp DebugMessage: Unallocated Mem: 129 bytes of memory from line 218 of F:\Projects\Kumquat3D\Source\parse.cpp DebugMessage: Not all memory has been freed from memory system Parse. DebugMessage: 258 bytes of memory still allocated. DebugMessage: Unallocated Mem: 21 bytes of memory from line 1227 of F:\Projects\Kumquat3D\Source\EntryField.cpp DebugMessage: Unallocated Mem: 21 bytes of memory from line 1227 of F:\Projects\Kumquat3D\Source\EntryField.cpp DebugMessage: Unallocated Mem: 21 bytes of memory from line 1227 of F:\Projects\Kumquat3D\Source\EntryField.cpp DebugMessage: Unallocated Mem: 21 bytes of memory from line 1227 of F:\Projects\Kumquat3D\Source\EntryField.cpp DebugMessage: Not all memory has been freed from memory system EditFields. DebugMessage: 84 bytes of memory still allocated.
Reply #2 from Elemental Forums Top

Actually, this too has been reported.

Most of those memory messages in debug.err probably don't matter.  Lots of stuff gets created once at the beginning of the game and isn't freed by game close. 

The real problem is game assets that are created regularly during turns and such, and aren't freed regularly.  That's where the memory leak occurs.  However, only SD could figure out where exactly those problems are.

Galactic Civilizations IV
Reply #3 from Elemental Forums Top

I will send my debug into tonite but it seems update .23 has not resolved this much. Memory out message after hitting Level 2, with 3 cities built, with my SOV.