memory leak somewhere in planetary invasion sequence

get to a point late in the game where you are getting invadded a lot.
open the task manager.
click through several dozen invasions.
go back to the task manager.
you will see that memory usage steadily increases while going through the invasions. eventually, the game runs out of memory and planetary invasion no longer works (transports go up to the planet but no invasion happens). at this point, several other dialogs don't work, including starbase construction.

I have 2 GB of real RAM and a 4GB swap file. should be plenty...
6,533 views 5 replies
Reply #1 Top
I am experiencing the same problem.

After AI invades my planet, I experience massive slow downs in the game. Scrolling becomes sluggish and menu buttons stop responding.

If I click Turn, game practically halts. Reloading doesn't work. Can't even pull up Load/Save menu. Data screens/Ship design can still be opened however.

I cannot attack AI and AI cannot attack me, even in ship battles.

Reply #2 Top
I too am having this problem, except that I'm the agressor. It really sucks.

Basically, I'll launch a whole slew of invasions, but I don't notice any slow down until the last two or three. First it takes a while for the invasion options screen to pop up (mass drivers, mini soldiers, gas warfare, etc.). Eventually it pops up. The next invasion take a while for the invasion options to pop up. Then it takes even longer for the resolution of the battle thing to show up. Third time, it just doesn't work and essentially prevents me from doing anything short of rebooting.

Reply #3 Top
I know this is an old thread but I was experiencing this exact problem in DL. The first 10 invasions everything is OK. At the 11th the hard disk light would go crazy. The pop-up would take a long time to load, and response would severely lagged. Restarting the game would aways solve this. But that was a pain.

I made a change to my system and the problem went away. I had my page file on a physically different drive than my system drive, my D: drive, and hard set to 3072Mb. I moved the page file to the C: drive and let Windows manage it, and the above problem disappeared. Go fig. Doesn't make sense to me, but it worked.
Reply #4 Top
I had my page file on a physically different drive than my system drive, my D: drive, and hard set to 3072Mb.


So I am assuming that you have more than one hard drive, correct? If not, then how the heck did the virtual memory go to a 'different' drive? Just have to ask since I'm pulling out my hair trying to get a stable running game.
Reply #5 Top

I had my page file on a physically different drive than my system drive, my D: drive, and hard set to 3072Mb.


So I am assuming that you have more than one hard drive, correct? If not, then how the heck did the virtual memory go to a 'different' drive? Just have to ask since I'm pulling out my hair trying to get a stable running game.


Yup, 2 different drives, 2 different manufacturers. In the virtual memory manager (I'm assuming you know how to get there) you can select any hard drive on your system and set a min and max amount of VM or let the system manage it.