[crash] Out of Memory (debug.err included)

Hello,

 

I am having a problem with the game getting an our of memory error after awhile. I have gotten it twice in the same game, but not at the same time. First was last night at around turn 200. Second time was tonight at around turn 300. 

Yes I am running win7 64x and have ATI cards. Yes I get the alt-tab error, but not going to do a separate post. 

Someone said running Task Manager with Commit Size option open could be helpful, but I forgot to watch it as I got into the game...

I have two files, first the zip file that has a huge name and the debug.err file in it:

http://dl.dropbox.com/u/10475251/Elemental1_00-2010-08-23T20-47-36-952.zip

Second I took a screen shot of the out of memory error message and more importantly the Task Manager on my second monitor that shows how much stuff elemental is using when it ran out of memory:

http://dl.dropbox.com/u/10475251/Elemental%20out%20of%20memory.jpg

I've never used dropbox before so I hope it works. 

Need anything else from me, just ask.

 

Thanks for making a fun game,

Nathan

 

5,880 views 8 replies
Reply #2 Top

Ok, first off. The new 1.05.016 patch is awesome. The game has really come together now and is much much smother. A few very minor details I'll point out later, but for now the only major problem is still the out of memory error.

 

I started a new game with the 1.05.016 version on a med map. Going great until turn 280 and I got the out of memory error. Yes, I updated to the latest ATI vid driver before playing. I'm running 10.7 version of Catalyst. 

Also I saw that the debug.err had my processor at ~2.7GHz's. Thats correct for the base, but I have it OC to 3.36GHz's. Not sure if that changes a thing....

 

New debug.err:

http://dl.dropbox.com/u/10475251/debug.err

It does auto save enough that I can just start very close (previous turn actually) and continue to play, but this 'forced break' is kinda annoying. 

Thanks,

Nathan

Reply #3 Top

Also I saw that the debug.err had my processor at ~2.7GHz's. Thats correct for the base, but I have it OC to 3.36GHz's. Not sure if that changes a thing....
End of quote

The top of the debug.err is just what DirectX reports.

Catalyst 10.8 is out today, give that a try and let us know if that helps any.

Reply #4 Top

It seems that the memory error has been fixed!

Thanks!

Reply #5 Top

Still got the error here, using Catalyst 10.8 to no avail.

Reply #6 Top

Out of memory in Tile Creator when i was playing around with it.

 

Debug.err

Reply #7 Top

I just did some experimenting. All the mipmap errors in the debug.err vanish if you set mipmap levels to 1. I got an extra 70 turns out of my game with this and i had almost 800 units and 31 cities on the screen.

Reply #8 Top

Ah, I spoke too soon.  Started a new game, almost got to turn 300

 

new debug.err

 

Maybe it is for the better, its almost 3am and I should have gone to bed hours ago....

 

Nathan