Hey everyone,

Not sure if anyone is having this issue, but I’ve been trying to figure this out and am out of ideas. Mu0n also gave some suggestions (thanks Mu0n!) but it hasn't worked yet. I’ve been having this error message (below) every time I load up VASSAL, even the most recent 3.2.15 version with 5.2.3 X-Wing Module:

”The maximum heap size stored in your Preferences for this module is too large. In particular, the maximum heap size must be less than the amount of physical RAM in your machine. The failsafe initial heap size of 128MB will be used instead. Please decrease the maximum heap size in your Preferences, and restart VASSAL.”

My preferences is set at 128 for both fields, and I even uninstalled VASSAL and reinstalled both the engine and the module, and I’m still getting this error. I have 8GB of RAM (on Windows 7) and easily have enough memory for 128MB. This has been causing issues with firing arcs and movement, where I stop having the ability to see my firing arc (ships disappear and error messages about memory size pop up 2-3 times in a row) and have to rely on the other person to tell me about my arcs.

I don't understand how my "max heap size" could be "too large" if it's set to the same value as the "failsafe heap size". Setting it larger causes the same issue, even though I have plenty of physical RAM (4 GB free right now)

Does anyone know if there’s a solution for this or if there’s something I can do to fix these memory issues?
http://screencast.com/t/rbHNisTHgyB

Thanks everyone!

That runs on Java right? If so, have you tried installing the latest version of the Java SDK?

It's the new K-Wing. Vassal isn't capable of rendering so many knickknacks.

I have my settings as:

JVM initial heap: 1024

JVM max heap: 4096

I only use 2 zoom levels, fit to height and 100% (to check close calls on collisions and obstacle landings), without cycling through every zoom levels in-between. If you use more, you can trigger those warnings more because I think VASSAL caches more versions of images in memory, one for each zoom level used.

setting it as low as 128 MB will definitely not be enough to load the images necessary for a normal 100 pts game, I believe.

That runs on Java right? If so, have you tried installing the latest version of the Java SDK?

You don't need the full SDK, which is huge and useful for developpers in Java. The JRE (Java Runtime Environement) is what you minimally need to run java applications such as vassal, without getting the developper tools bloating.

That runs on Java right? If so, have you tried installing the latest version of the Java SDK?

No, just the latest version of JRE

I have my settings as:

JVM initial heap: 1024

JVM max heap: 4096

I only use 2 zoom levels, fit to height and 100% (to check close calls on collisions and obstacle landings), without cycling through every zoom levels in-between. If you use more, you can trigger those warnings more because I think VASSAL caches more versions of images in memory, one for each zoom level used.

setting it as low as 128 MB will definitely not be enough to load the images necessary for a normal 100 pts game, I believe.

Yeah, I had it set at 1024 and 4096 in the past, but it doesn't get rid of the error messages and I still get the memory issues when I turn on the firing arcs sometimes. I think the error message is complaining that I'm setting my heap size "too big", even though it's the exact same size as the failsafe heap size of 128 MB.

Very strange...