[messages] [Technical Support & Bugs] Can't save log files error has recurred

Joel Uckelman uckelman at nomic.net
Sat May 6 01:07:44 CEST 2017


Thus spake Edrains via messages:
>
> 2017-05-05 08:28:17,219 [0-SwingWorker-pool-26964746-thread-1] INFO 
> VASSAL.tools.io.ProcessLauncher - launching C:\Program Files
> (x86)\Java\jre1.8.0_111\bin\java -Xms512M -Xmx1024M -DVASSAL.id=1
> -DVASSAL.port=52407 -Duser.home=C:\Users\grains -Duser.dir=E:\VASSAL -cp
> lib\Vengine.jar VASSAL.launch.Player --load -- E:\VASSAL\The Battle for
> Normandy 3_16.vmod
> 2017-05-05 08:28:17,279 [0-SwingWorker-pool-26964746-thread-1] INFO 
> VASSAL.tools.io.ProcessLauncher - launching C:\Program Files
> (x86)\Java\jre1.8.0_111\bin\java -Xms64M -Xmx128M -DVASSAL.id=1
> -DVASSAL.port=52407 -Duser.home=C:\Users\grains -Duser.dir=E:\VASSAL -cp
> lib\Vengine.jar VASSAL.launch.Player --load -- E:\VASSAL\The Battle for
> Normandy 3_16.vmod

Here's what's happening:

The first line shows the module being opened with a max heap of 1024MB.
That _fails_, which is why the second line shows the module being
opened with the failsafe max heap of 128MB, which isn't enough to use
this module properly.

I think what you're seeing is that sometimes Java is able to claim
1024MB of contiguous memory, in which case the module opens successfully,
and sometimes it isn't, in which case you get the result you saw above.

It's the _contiguous_ part here which is important. You probably do have
more than 1024MB free memory when you try to load the module, but
sometimes there isn't a large enough contiguous chunk available.

Suggestions:

1) Try setting the max heap a bit lower.

2) Install more RAM.

-- 
J.


More information about the messages mailing list