1.6 Full, Memory Crash

STARDOCK why haven't you fixed this problem, and why can't you fix this problem, it has been a main bug in your lose code now from day 1. If you do not possess the talent to repair your own very messy code then why will you not seek professional help to do it for you. Carrying on the way you are by ignoring this very large bug will only result in the rapid reduction of your reputation and customer confedence and a dirty great black hole in your bank account.

I'm having the same memory leak issue. A game with a small universe that runs under a couple of hours is fine. But if a game goes on for more than that time, I eventually get an out of memory error, even though I'm carrying 3MB of RAM and plenty of virtual space.

This is what you call a absolute disgrace. If your going to write a game, first you should make sure you are competent enough to finish the project (bug free).
All forward motion on this game should stop until they have tracked down and squashed this memory leak.
I don't think Ill be buying another game of these jokers.

lol, bug free? You must be new to PC gaming, Crosswire. Either that or you're a glutton for disappointment because there's practically no such thing as a bug-free release.

Heck, take some comfort from the fact that this game was technically "finished" a long time ago, and they've been improving it for free all this time.

Yeah, I'm getting random crashes too, albeit it's not from out-of-memory errors. At least that's not what it's telling me.

Okay, your right, no game is entirely bug free, but we are talking small work around bugs, bugs that are not show stoppers. This bug is a large hairy bug with long legs and a poisonous bite. It just for the life of me can't understand why they will take time to program in pink battle ships with lasers that fire candy floss, yet leave this problem unresolved, I mean don't the programmer/programmers take any pride in their work?
Maybe memory management is a weak point with them, if so seek help, even members/customers are trying to help and offer up suggestions, alas these suggestions seem to fall on deaf ears, maybe a pride thing hu!

Is this the error that says something about a memory buffer being triggered and the game is now unstable and then it shuts off?

How do you know it's the game's memory management? Windows is notorious for being incapable of managing it's memory effectively, let alone efficiently. Part of the reason for the hundreds of third party memory managers out there.

I agree with Crosswire. As a matter of fact i stand behind his idea of hiring others to assist in areas that one might not be strong in. One must realize that their standards are their own. No matter how large the hair bristles on this poisonous beetle of buggy wrath may be, the shinny pink armor plating reflecting the rays of a distant sun as it gracefully orbits planet custom world while releasing minty candy floss into it's atmosphere is an Accomplishment (capital A) worthy of anyones praise.
Hold faith in stardock. They have disappointed the disappointed, upgraded the upgradeable, and provided a great product to the blind and clairvoyant alike!
ALL HAIL STARDOCK. KING OF THE AI!

How about posting a debug.err log so the community can try to help out? Without one, posts like these seem to be simple gripe sessions.

The memory issues have been under constant investigation all the while. A number of changes have been made in attempt to combat the memory issues, but while the devs think they have a handle on *what* is being leaked, the where as yet remains elusive. The trouble is that the leak-debugging tool refuses to cooperate, which leaves little else but to go through and search manually. And that's not at all an easy or fast task when it's an issue that seems to only manifest on large or full games.

At any rate, insulting the devs is not what I'd call helpful motivation.

Tracking down a memory leak is a very difficult task to do with tools, much less manually. Let me just say that if the enterprise software I use was supported as well as Stardock supports GalCiv2, I wouldn't push freeware open-source software as much as I do. For goodness' sakes, they just rewrote large portions of their graphics engine to provide better performance for people with older rigs. That kind of refactoring is usually hard as anything to justify to management, even though in the end it drives customer loyalty, marketshare, and ultimately revenue.

Just curious: what is your Windows pagefile set to?

debug.err log have been posted by the millions, every conceivable page file config has been tried and yet the problem persists. Seems the only way to play this game is by downgrading your computer.
I wouldn't call what I have said as insulting the devs, I'm just having a dig at their work and want to know what they are doing about it. They can't tell me they are putting every waking hour into tracking down this leak when they are constantly adding stuff and selling expansions. This problem should have been sorted before they even thought of releasing DA, and that's the truth.

It seems to me reality trumps should haves and could haves. If this problem is what they said it is (99% chance that it is) then every waking hour going into a bug that has persisted this long would actually be counter productive. Stardock has made the right decision. Correct choices have to be made along the way. As you build your Empire do you make sure that all aspects of it are running at 100% or do you notice how if you attempted this you'd fall behind the competition and become yet another conquered empire(corporation)? Failure is not an option. Stardock has jumped the hurdles others still dream to jump. They have dove deeper with less protection than the horniest well endowed american virgin in brazil. There is no difficulty setting in the real world.

Again, can you post a debug.err log so someone can perhaps help you?

Out of memory and choppy gameplay once the game has been running for a while are known issues. I eliminated the out of memory error by upgrading to a full 4GB's which XP only sees 3.25 of it but its enought to stave off that error. But now as the game progresses it becomes unbearably choppy as it can take over 10 seconds from clicking on a ship or fleet for it to actually register - even when its the AI or the game auto selecting ships and stuff. CariELF is looking into my issue under beta reports but has handed it off to their 3D guru which I believe will not solve the matter. I can disable every graphic effect but the problem persists and has done so for several people.

All I know is if they cannot fix it soon I will have to see about down grading back to 1.5 for GC2DA where the problems did not exist.

Maurice

I must say you are a placid lot, any other game with this problem, going on for so long and the forum would be positively blue.

Memory issues have been a high priority for us.  Yesterday, I was able to finally track down and fix a major memory leak.  You can get a test build here:

https://forums.galciv2.com/?forumid=357&aid=155043