Slow recovery after exit from game

HP Pavilion zv6000 laptop with AMD64 3200 CPU, ATI Radeon Mobility X200, and 512MB of RAM running Windows XP. Swap file is at 765MB. General observation: the game seems to run hot (GPU throttling?). When I exit from the game (even on a tiny map, I'm afraid to try a larger one right now) it takes a good 30 seconds to a minute to "come back" to Windows. Lots of "tool tips" have popped up on the desktop but the screen flickers and they go away. (This is stock XP, I'm not running anything funny beyond AVG antivirus and the stuff that came with the laptop). At one point it looked like it said that Windows adjusted the size of the virtual memory. Is this a sign of a memory leak? The slow recovery is reproducible on every exit; but I'm not sure the same message flickers each time. The HDD is thrashing, so I expect so. Any thoughts?
9,841 views 8 replies
Reply #1 Top
Weird. I just got a new laptop from work, Dell 810 with only a 2.13GHz / 1GB DDR2 / X300 64MB, and quitting GalCiv2 takes less than 3-4 seconds. My desktop is immediately responsive. This is also with SQL Server, Norton AV, Sygate Firewall, VM, VSS, and other services all consuming memory in the background (and a few CPU cycles here or there.)

Your machine really shouldn't take that long to exit the program.
Reply #2 Top
There is a known overheating issue that will be fixed in the next patch.

-Dewar
Reply #3 Top
While the game can use a whole lot of memory (1.1 is the peak I've noticed), at least for me it doesn't seem to exit slowly. Pretty quick, actually. I play the Sims 2 a lot and that can take minutes to unload.
Reply #4 Top
I have an AMD Turion 1.8Ghz, x200, and 1gb of RAM and the same happens to me. I find it generally occurs after a program has used a large amount of RAM. Hopefully the next patch will add a lot of options to manually turn down graphics (I never trust auto-detection).
Reply #5 Top
I have a P4, 1gb ram, the game quits very fast, it literally blinks back to windows, but then, it takes about 30 seconds for windows to work properly (the desktop).
Reply #6 Top
From what I'm reading, this issue may be limited to AMD64 CPUs or possibly 64-bit CPUs in general... OR it could be the Radeon Mobility X200 GPU... anybody with an EMT64 that's having this or a non 64-bit CPU but a X200 that doesn't have it happen?
Reply #7 Top
Also, for me it does NOT do this if I am not in a game... if I just go into the menu and back out, things pop back to normal pretty quick. For those who have this, is that your experience too?
Reply #8 Top
The latest 10X.009 patch does not seem to fix this problem for me. Does it still happen to anyone else?