Re: Re: Re: Re: Re: Re: Re: Re: Re: Huge is Too Small
Oh the game definitely leaks memory, and that's another sure fire way to get a crash sooner or later. I'd definitely say that leaking memory somewhere in a calculation would be a very quick way to cause a crash when scaling up to a larger size map (and more intense use of whichever calculation is leaking memory), and I guess as I think about it, that's a pretty likely explanation for the sort of problem behavior you're seeing.
So now that I think about this possibility, I bet what you're running into is that you play in some way differently than I do, and you hit the memory leak more often. Maybe you look at some screen I don't, or you use more of some kind of military unit than I do, and so you're tripping over some bit of bad code over and over that I'm just lucky enough to avoid.
Sad thing is ... the tools for detecting and fixing memory leaks are so good these days ... they really shouldn't have such problems.
Originally posted by Willem
Not always, towards the end of the game I get periods of lag and jerkiness. However that clears up for awhile if I quit the game and restart. It could be symptoms of a memory leak, though I don't know enough about that to comment informatively.
Not always, towards the end of the game I get periods of lag and jerkiness. However that clears up for awhile if I quit the game and restart. It could be symptoms of a memory leak, though I don't know enough about that to comment informatively.
So now that I think about this possibility, I bet what you're running into is that you play in some way differently than I do, and you hit the memory leak more often. Maybe you look at some screen I don't, or you use more of some kind of military unit than I do, and so you're tripping over some bit of bad code over and over that I'm just lucky enough to avoid.
Sad thing is ... the tools for detecting and fixing memory leaks are so good these days ... they really shouldn't have such problems.
Comment