Do you maintain a module that is prone to run out of memory? Typically, this is discovered when a user comes to close a log file after a full game or many actions, even if the game itself runs ok. Most modules aren’t affected, as the Vassal default of 1024Mb is more than enough unless pieces in the game have an exceptional number of traits.
However, if you’re still reading, then you may want to try out a build for your platform from here, using a test copy of your module. Note: If you’ve arrived here after some days, you may need to page forward until a list of builds appears, due to the way the filter works.
These builds are a test of my recently proposed Vassal update that will allow module designers to specify a minimum setting for JVM maximum heap. It works via a new Global Option setting.
To test,
- make a copy of your module and open that copy for edit.
- In Global Options, set the JVM field to the value you need.
- Save the module.
- Thereafter, you should find that any attempt to start the module with a lower JVM Maximum Heap user setting (in Preferences, General) should result in that setting being overwritten and advice to that effect appearing in the chat log. e.g.:
I hope this change, or some equivalent, will eventually help us help our users to avoid this issue in future. Your feedback would be appreciated.
Note: This article addresses core game memory requirements, the limit of which is set in the module Preferences. The Convertor and Tiler memory allowances, set in the Vassal Module Manager, are not affected.