Gamecrash, maybe memory leak

from GalCiv2 Forums
After about 3 hours of playing the gamescreen begins to flicker and then the game freezes. I minimized the game afterwards and spotted a warning from windows about not enough virtual memory in the systray so it might be that i got a memory leak somewhere. After i minimized i could watch galaciv in the process manager that it released about 2 mb of ram per second until it suddenly disappeared. (before the crash i started an invasion)

here are my pc-stats from the errorlog:

Debug Message: Version v1.0D-1 Digital: Bonus Pack last updated on: Fri Feb 24 12:35:33 2006
Debug Message: Could not find a TGN Serial No.
Debug Message: *********DXDiag info follows.*********
System Info
Time: 2/26/2006, 08:35:12
DirectX Version: DirectX 9.0c (4.09.0000.0904)
Machine Name: PCAL
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Languages: German (Regional Setting: German)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: BIOS Date: 09/24/04 16:10:38 Ver: 08.00.09
Processor: AMD Athlon(tm) 2400+, MMX, 3DNow, ~2.0GHz
Physical Memory: 510MB RAM
Page File: 320MB used, 927MB available
Windows Dir: C:\WINDOWS


Display Info
Display device 1:
Device Name: \\.\DISPLAY1
Card Name: RADEON 9600 SERIES
Manufacturer: ATI Technologies Inc.
Chip Type: ATI RADEON 9600 Series AGP (0x4152)
DAC Type: Internal DAC(400MHz)
Key Device: Enum\PCI\VEN_1002&DEV_4152&SUBSYS_C01A1043&REV_00
Display Memory: 128.0 MB
Current Display Mode: 1152 x 864 (32 bit) (100Hz)
Monitor Name: SONY CPD-E400P
Monitor Max Resolution: 1800,1440
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6599
Driver Date: 1/25/2006 04:52:48
DirectX Acceleration Enabled: Yes



Sound info
Sound device 1:
Description: SB Audigy 2 ZS Audio [EF00]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04
Manufacturer ID: 1
Product ID: 100
Driver Name: ctaud2k.sys
Provider: Creative
Driver Version: 5.12.0001.1164
Driver Date: 12/8/2005 11:55:46
Type: WDM
Other Drivers:
Acceleration Level: 3
Cap Flags: 0
Min/Max Sample Rate: 0, 0

and the part where it crashes looks so:

Debug Message: Updating ZOC.
Debug Message: Random Event: Begin
Debug Message: FleetCombat_Ships_Entry_Status setting size 56 x 0
Debug Message: FleetCombat_Ships_Entry_Status setting size 56 x 0
Debug Message: FleetCombat_Ships_Entry_Status setting size 56 x 0
Debug Message: FleetCombat_Ships_Entry_Status setting size 56 x 0
Debug Message: FleetCombat_Ships_Entry_Status setting size 56 x 0
Debug Message: Destroying ship Defender M4-3 1565. Orbiting: 1
Debug Message: Was Orbiting: Hestia IV
Debug Message: Destroying ship Defender M4-3 1565. Orbiting: 0
Debug Message: Destroying ship Transport 1497. Orbiting: 0
Debug Message: Destroying ship Transport 1479. Orbiting: 0
Debug Message: Destroying ship Transport 1453. Orbiting: 0
Debug Message: Destroying ship Terran Fleet 186. Orbiting: 0
Debug Message: Error flipping back buffer to primary buffer.
Debug Message: Driver internal error

now comes this about 1000 times:
Debug Message: Error flipping back buffer to primary buffer.
Debug Message: Driver internal error

then:

Debug Message: Error flipping back buffer to primary buffer.
Debug Message: Driver internal error
Debug Message: WM_CLOSE message received.
Debug Message: GameUninitialize start
Debug Message: Killing Galaxy
Debug Message: Killing threads.
Debug Message: Kiling civs.
Debug Message: Killing ships.
Debug Message: Killing rallypoints.
Debug Message: Killing misc objects.
Debug Message: Killing stars.
Debug Message: Killing anomalies.
Debug Message: Killing space resources.
Debug Message: Killing colonies and planets.
Debug Message: killing scenario.
Debug Message: Clear galaxy settings.
Debug Message: Clear influence.
Debug Message: Clear up laws.
Debug Message: Clear first time events.
Debug Message: Clear wonders and trade goods.
Debug Message: Clear sector mapper.
Debug Message: Clear data definitions.
Debug Message: Killing Galaxy: Completed
Debug Message: Desplay_ShipList_Entry_Down.png not cleared 90 counts left.
Debug Message: Desplay_ShipList_Entry_Over.png not cleared 90 counts left.
Debug Message: Desplay_ShipList_Entry_Up.png not cleared 180 counts left.
Debug Message: Desplay_Small_Status_Frame_Up.png not cleared 180 counts left.
Debug Message: Gfx\Overlays\Starbase_Mill_48.png not cleared 29 counts left.
Debug Message: Gfx\Overlays\Starbase_Mine_48.png not cleared 7 counts left.
Debug Message: Gfx\Overlays\Starbase_Res_48.png not cleared 41 counts left.
Debug Message: Gfx\Overlays\Starbase_So_48.png not cleared 13 counts left.
Debug Message: TextFiledBack.png not cleared 180 counts left.
Debug Message: GameUninitialize end
Debug Message: Device not cleared. 84 counts left.
Debug Message: D3D not cleared. 1 counts left.
Debug Message: Destroying Window.
Debug Message: Main Shell terminating normally
Debug Message: Unallocated Mem: 8 bytes of memory from line 1135 of .\Source\editfields.cpp

now this line about 1000 times
Debug Message: Unallocated Mem: 8 bytes of memory from line 1135 of .\Source\editfields.cpp

and in the end:

Debug Message: Unallocated Mem: 8 bytes of memory from line 1135 of .\Source\editfields.cpp
Debug Message: Not all memory has been freed from memory system EditFields.
Debug Message: 2160 bytes of memory still allocated.
Debug Message: Unallocated Mem: 1024 bytes of memory from line 1320 of .\Source\memman.cpp
Debug Message: Unallocated Mem: 1024 bytes of memory from line 1320 of .\Source\memman.cpp
Debug Message: Unallocated Mem: 1024 bytes of memory from line 1320 of .\Source\memman.cpp
Debug Message: Not all memory has been freed from memory system UIGame.
Debug Message: 3072 bytes of memory still allocated.

hope this helps
6,102 views 5 replies
Reply #1 from Stardock Forums Top
I've had the game crash on me yesterday after hours of playing. It started loading loudly from the hard disk during the last turns and then finally crashed. It does sound like a memory leak :/
Reply #2 from Stardock Forums Top
Not necessarily, but possible. I think they got the memory leaks well locked down in beta
Sins of a Solar Empire II
Reply #3 from Stardock Forums Top
What else did you have running in the background? I know Mozilla Firefox can be a memory hog if its left open due to its page cache. The combined load on the system could have used all the main memory and page file causing the crash.
Reply #4 from Stardock Forums Top
the biggest program running in the background was the ati driver. there was no other "real" program open
Reply #5 from Stardock Forums Top
With my Vista 64bit PC, the game has a bad memory leak. It does not appear to be a problem on smaller maps, but on the giagantic map it is a problem.

The game itself will use 1.3GB of RAM which is not horrible but when it hits the 100% mark of the 2GB in my PC, I get an out of memory error and the game crashes.