I am noticing something odd about the behavior of the VolatileImage class in my game. I am using a Frame with a BufferStrategy in exclusive screen mode on Windows machines. I want to use a pretty good amount of VRAM and manage that directly with VolatileImage objects.
When my game is put into the background - using the Windows key, for instance - the heap space spikes quite noticeably. It seems that the JVM wants to preserve the VoltileImage surfaces by copying them back into system memory.
My question is: can I do something to prevent this? Obviously, because my application is a game I am happy to manage restoring the VolatileImage objects’ surface myself. And, of course, there is no reason to do that when the game is minimized anyway.
All of this seems to happen BEFORE my frame receives the windowDeactivated message, by the way.
Any ideas?
Thanks!