This is definitely a memory leak going on in the heap. I presume this is caused by Vassal not Java itself, but from a bit of searching, it seems to be not uncommon in Java apps.
Still looking for suggestions on how to fix/counter it, and how to go about increasing memory allocation... /me bangs head on desk... --- In [email protected], "benw_h" <[EMAIL PROTECTED]> wrote: > > OK thanks - I can't actually work out how to increase the memory > allocation, and obviously cutting stuff is not very useful as it > effects the game. Are the limits relevant to what's on sreen or to > everything in the module? I might be able to split the extensions > into another module and treat it as two seperate games. Not very > elegant, but I am a bit desperate! > > --- In [email protected], "Brent Easton" <b.easton@> > wrote: > > > > Ben, > > > > >....and do any of the changes you make effect saved games already > in > > >progress? So far I've reduced the colours of all the maps. > > > > Reducing the number of colors in the map can reduce your file size > in the module (as long as you reduce it to <= 256 colors, make it > indexed and save it as a PNG), but this will have no effect on the > memory required by VASSAL to display those maps. > > > > The number and size of maps, counters and cards is really the only > issue. > > > > > > > > > All of my > > >pieces are already only 1kb (does it matter how many colours they > are > > >if they are already this small?). I'm still getting out of memory > > >errors. Does the sheer number of images in the module (even if not > > >displayed) effect this? The mod is about 25Mb (5+5 per extension), > with > > >probably around 5-600 piece images, 8 maps (with multiple boards > in > > >most cases), and another 200 cards. Any advice? AT present I've > truned > > >my attention to increasing the memory allocation... > > > > ____________________________________________________________ > > Brent Easton > > Analyst/Programmer > > University of Western Sydney > > Email: b.easton@ > > >
