OK - thanks for the clarification. I realised the manual install jar file would not fire (first reaction was to look for a bat or exe, hence inability to actually run the manual install), so I stripped off both Java and Vassal and started again. I'm re-installing as we speak, so I'll see if that works...
Original reason for believing it was a leak is that we can play for several minutes, and then it grinds to a halt. During that time we have actually been removing counters rather than adding any. --- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> wrote: > > No Ben, > > It is not a memory leak. > > Each image requires 4 bytes of memory for each PIXEL. A 75x75 counter requires 22K of memory. A 100x200 card requires 80K. A 2000x2000 ,map requires 16Mb. Then add additional for zooming (though this is in the process of being impoved). Add up for all images active in a game... > > The fix is to increase your memory allocation to at least 512Mb. This has been extensively documented in this email list (try searching the archives) and in the installation instruction for the new version you where pointed to. > > Regards > > > >*********** REPLY SEPARATOR *********** > > > >On 21/10/2007 at 1:51 PM benw_h wrote: > >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... > > > ____________________________________________________________ > Brent Easton > Analyst/Programmer > University of Western Sydney > Email: [EMAIL PROTECTED] >
