Memory Leak?

Harkonnen said:
The Great Apple
That .reg file was asked by someone here, you don't need to install it.

My .DLLs here were about logging activity on several systems - it doesn't fix anything yet.

A patch saving ~150Mb is going to be released tomorrow.
Cool...maybe I will chance re-installing the game if I have some time this week...;)

BTW, thanks to all for the reg info - I have not had too much time to look at them yet...sorry, work,....but they have been helpful, if only in that a value was not there...I am doing research and will test this week if possible that value...I do not want to publish it yet as it is one that does have piotential security risks if used, but may help stop BSOD's (it is only used in debugging normally).
 
Game crashes for me too later on. Every time. 2k support ran me through 4 different possiblities including memory leak that was supposed to be fixed with the most recent patch. I really have the impression that there was a colossal blunder that is not likely to be fixed. Oh well...good games you cant play turn into crappy ones quick...good luck to you all.
 
Yep, definately a memory error.

Harkonnen, I think you may have a bit tougher time fixing this problem. Hopefully the developers will find this useful - although they should be piping this info to a log file and not the GUI. I've had this error come up quite a few times with my most recent game. It seems to be associated with saving games. This particular screenshot came when I tried to do a manual save - but it would often appear about the time an autosave was due to kick in.
 

Attachments

  • error.JPG
    error.JPG
    44.2 KB · Views: 817
KingsSon
Please post your savegame here of if is too large, mail it to 'headden@karelia.ru'. Thanks!
 
I'm getting the exact same error as KingsSon. Using Harkonnen's patch last night I didn't have any problems at all at first. Then I set the vid_mem_usage to 400 just to experiment, and I got this error after a couple of turns. Changing the vid_mem_usage setting back to 180 doesn't help though...the error still comes up after a couple save attempts. I'm not sure if changing the vid_mem_usage had anything to do with it, but it does seem kind of suspicious. I don't know why it would still be coming up though.

Maybe someone at Firaxis should look at that line in the code. Maybe this was always the problem but the error mesage was never seen, and Harkonnen's patch has done something to make the error message show up (and only when saving)?
 
Ribannah said:
There is no memory leak, as far as I can see. The game runs an entire day on my 256K RAM. However, there seems to be something else: each time you use a new feature, like an advisor screen, it gets loaded into memory and then stays there. So the more features you use during a session, the more memory is claimed by them. If you quit and reload the game the memory will be clear again.

I don't agree with this statement. I have quit and reloaded the game and the game reallocated the same 500+ MB of virtual memory. I do think there is a leak and a patch must be issued soon. It is making the game unplayable and is a nuisance.
 
eagle0468
Preallocation depends on map size at least... For example, small map is entirely loaded into mem while huge map is loaded on-the-fly. As I have spotted, it loads map regions as per country/island/continent when you scroll to it.
 
BlueLikeYou
Yes, it is possible... That messagebox requires some few geometry data just to render it. Probably my patch leaves enough video memory or at least it is not corrupted enough, so the message is shown, otherwise it silently CTDs... Just a guess.
 
BlueLikeYou said:
Maybe someone at Firaxis should look at that line in the code. Maybe this was always the problem but the error mesage was never seen, and Harkonnen's patch has done something to make the error message show up (and only when saving)?

It wasn't Harkonnen's patch that made that error visible. That's the exact same error message I've been getting just about every time I've managed to play to 1500AD or beyond (before using Harkonnen's patch, I'm just now reading about it for the first time). Never seen the message in an earlier stage of the game though.
 
Sorry for the late reply - Harkonnen I'll email you a copy of (one) of the save games so you can play with it.

However, as Borlag noted, this error message didn't come up because of the patch you've created. I haven't changed any of the .ini settings, nor have I tried the utility.

Borlag, when do you usually see that message? As I posted previously, mine comes up often when I try to do saving. I've also noticed that the save game is corrupted when this happens.

Upon further investigating (er... playing) there seems to be a variable amount of time between crashes. It would crash sooner (ie not long after I restarted) when I would prepare a large invasion against my neighbors, by moving a bunch of units around the map. Is it because of accessing a large number of units? Moving to many places on the map? I'm not sure, but I'll keep noting when the defect seems to occur. Also - it didn't start crashing until recently - as in after 1500.

I love the game, but to be honest these crashes are completely unacceptable. I am a software developer. It is irresponsible and unethical to release a product which has these kinds of problems. 2K/Firaxis may have my money, but they have lost something far more valuable - my trust.
 
Well, I've only played it 5 times now and apart from one instance of a total reboot, each and every other time it has crashed with that error message.

I tend not to bother with saving games unless I'm quitting for the day, otherwise I rely solely on autosaves if there's crashes and such. I'm not really sure if those crashes happened while doing the autosaves, but just incase it happens again, I'll try to check out for that also.
 
BlueLikeYou
I have mailed you back. Basically, I've got BSOD several minutes later after pressing next turn, the last thing I saw was diplomacy screen.
 
Just upgrade the RAM to 2GB or more. Just until Firaxis can fix this memory hogging issue. I had 1 GB and it crashed constantly after 1988. Now, with 3GB of memory, not one crash. I'm up to 2027 and no crashes. Memory consumption for the game is up to 653MB. I'm thinking more and more that this game was built for the new hardware that is out on the market now.
 
Back
Top Bottom