Well, I tried a small game on the Windows machine. I had all of the effects settings maxed. I played the game through to the end, and I took my time. The game ran several hours and didn't climb much over the 1.3GB it used at the beginning. So much for the Windows memory leak theory! Sorry for jumping to conclusions. I'll let the Wine folks know my results.
Well, if the explanation at the winehq link is correct, it should look like any other memory leak on Windows. I never noticed a problem with SoaSE on my Windows Vista64 machine (other than a slowdown with battles between hundreds of ships). That machine has 4GB system RAM and 512MB video RAM. My Linux/Wine machine has 6GB system RAM and 1GB video RAM. Outside of Wine, I don't have much visibility into what is going on. I suppose in Windows, all I have is Task M
I am trying to run SoaSE on Wine. I am having a problem in which the SoaSE gets an out-of-memory error (GL_OUT_OF_MEMORY) from the Direct3D subsystem. I know Wine and Linux are not officially supported platforms for SoaSE, but I have reason to believe this problem exists on Windows as well. There is a pretty good description of the problem at this link: http://bugs.winehq.org/show_bug.cgi?id=16456#c4 The gist is that there is a texture memory leak in SoaSE.
Sins Forums