If the game client starts to use more than 1GB of memory, that message is fired.
You could be running a system with 2 GB of physical ram and get the message when it hits 1GB or you could be running a system with 32GB of ram and get the same message.
The problem is the video engine is loading all the textures into the clients memory pool but doesn't clear them out properly and starts behaving erratically past the 1GB mark . Rather than fixing the issue with the engine, this message was slapped into the game instead.
The biggest issue is that the game has 10GB of assets but a memory pool that barely works with 2GB (and at a technical best of 4GB due to 32bit limitations)
A real sysadmin knows how to change the time.
If you make the same mistake while trying to make up for the previous one, you are doing something wrong.
As much as I'd love to say I offer consulting services, the scope of things broken is too large.
