Thus spake "Rodney Kinney": > > I suppose that one can, effectively, do this by careful specification > > of the minimum and maximum sizes. I'm not sure what the limits of > > the JVM are for memory, but something like a minimum of 32 or 64 MB > > and a maximum of 2 or 4 GB should do it. > > > I always figured that if you tell Java it can use more memory than the > system actually has, Java will crash hard when it tries to grab memory that > isn't there, as opposed to the fairly graceful failure/error-dialog you get > now. That's the reason not to just bump the allocation to 4GB. However, I > don't actually know that this is the case. If we can establish that it's > safe to, say, give 2GB to Java on a system with 512MB RAM, then I'll happily > bump up the default allocation. > > rk >
I think I know what would happen on my Linux system: The real limit is the amount of RAM plus swap. E.g., my desktop has 512MB RAM and 1GB of swap. If Java allocated more than 512MB of memory, some of it would necessarily be swap and that would likely result in a bit of thrashing. It would still work, for some value of "work", but it wouldn't work well (I'm guessing). Whether it's safe depends both on how much swap there is and how much memory is already allocated when VASSAL starts. What if we set the maximum memory allocation to some fraction of the user's total RAM, say 0.5? (This happens to be what I do in practice.) -- J.
