[messages] [Module Design] check boxes indicating a memory leak issue?

Brent Easton b.easton at exemail.com.au
Thu Aug 13 01:15:32 CEST 2015

I think you've pushed the engines past their design specs captain!

The problem is not a memory leak, it is from making the damage check
sheet counter too complicated. You can only add so many layer and other
traits to a counter before it starts affecting performance of the Vassal
system as a whole. It is a fundamental design limitation of Vassal 3. 

If there only a limited number of these damage check sheets, then you
can get around this by creating each one as a Map within a Chart tab,
and create each checkbox as a separate counter.

The other alternative would be to create a custom Java trait for the
damage sheets.


Read this topic online here:

More information about the messages mailing list