Suspected Memory Leaks

[Feltan]

I have observed in large scenarios (> 1000 AU), that over time game performance diminishes. I tend to run games a long time (>4 hours). Also, when one saves such a large-long game, quits the application, and then restarts the application the performance will dramatically improve.

From the outside looking in, such behavior is indicative of a memory leak with the application.

I do not have the tools or access to evaluate this for you. However, just a heads up that I suspect you have garbage building up in memory as a large scenario progresses.

Regards,
Feltan

[chesmart]

Agree Feltan have the same prob on larger scenarios

[Dimitris]

Thanks guys. If you can post up the scenarios under which you are observing this issue it would be great. (I suspect this result from actions that may be scenario-specific, e.g. excessive pathfinding). We can then investigate this as time and resources allow.

Thanks!

[Feltan]

Sunburn,

Attached per your request. However, my experience/observation is that any large scenario run for a long time will exhibit this behavior.

I hadn't thought about path finding. The events I have noticed were after large engagements, and thought perhaps the app was not cleaning up destroyed units memory allocation -- especially guided missiles. But that is just a hunch.

I am not sure what language you code this game with, but if you don't have auto clean-up (like in C or C++) you are bound to get some leakage. Even if you do have auto cleaning, it happens with larger programs all the time, and it is a PITA to find an fix.

In the attached scenario, you will need to run/play it for around 4-6 hours before you note that performance is bringing to its knees. Save, restart the app and load the save. Everything is perky again.

Regards,
Feltan

[Dimitris]

Thank you!