Since GameGuru is long-running and does a lot of allocation and freeing. It's when you have mixtures of short-lived and long-lived objects that you're most at risk.

GG has allocation failures or unexpectedly causes the system to run low on memory, and you've ruled out memory leaks, perhaps malloc returning null.

Anyway this's old issue, sometimes before I had experienced thaat memory isuue with GG when minimized, and I should add that I've that issue just from time to time, not often.

I wonder myselft if for any chance it has something to do with 7018 error, since is too hard to find data, when all the blocks (chunks) are badly allocate, and you`ve a lot of memory block unusables, specially with virtual memory.



3com

If I let GG sit long enough it will crash with this error - even if I just start it fresh and let it sit. Pressing CTRL-ALT-DEL at any time will induce a 'memory fragmentation' crash. After the memory fragmentation crashes, GG usually 'recovers' to the same mostly water covered map every time, regardless of what map was being worked on previously. Other times after a 'recovery' the mouse cursor can click buttons and menus, but cant interact in the 3d part of the editor without some extra task-switching, or minimize/maximizing. I've noticed CPU utilization in the editor is much higher than in game. SAVE OFTEN!!!