World in Flames heap size loop

Using OSX; 8GB; Vassal preferences “importer” set to 1000MB (initial heap) and 3000MB(max heap)
Tries to open WIF: “Maximum heap size too large…failsafe will be used.”
Allow blue circle to spin for a while: “Out of memory…increase heap size”
blue circle renews spinning…back to “Maximum heap size too large…failsafe will be used.”

I caused this by intially setting heap to 500000MB (dumb, but I was finding it was taking forever to load)
I am stuck in a loop! Help!

Thus spake peterjfrigate:

Using OSX; 8GB; Vassal preferences “importer” set to 1000MB (initial
heap) and 3000MB(max heap)
Tries to open WIF: “Maximum heap size too large…failsafe will be
used.”
Allow blue circle to spin for a while: “Out of memory…increase heap
size”
blue circle renews spinning…back to “Maximum heap size too
large…failsafe will be used.”

If you’re using the Importer to load the WiF module, there is no heap
size setting which will work. This is because the Importer is for
converting modules in a foreign format (presently, only ADC2) to
VASSAL’s format. If you want to load a VASSAL module, use Open Module.


J.

Thanks for your reply. I am still struggling to find where the heap size is too large in the error log:

2017-07-30 10:04:30,482 [0-main] INFO VASSAL.launch.StartUp - Starting
2017-07-30 10:04:30,491 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.10.5
2017-07-30 10:04:30,491 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_121
2017-07-30 10:04:30,491 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2017-07-30 10:04:31,150 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2017-07-30 10:05:20,500 [0-SwingWorker-pool-1181550434-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file /Users/Sean/Desktop/8.542.vmod
2017-07-30 10:05:23,015 [0-SwingWorker-pool-1181550434-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2017-07-30 10:05:23,016 [0-SwingWorker-pool-1181550434-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module World in Flames Final Edition
2017-07-30 10:05:25,957 [0-SwingWorker-pool-1181550434-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Xms64M -Xmx128M -DVASSAL.id=1 -DVASSAL.port=59107 -Duser.home=/Users/Sean -Duser.dir=/Applications/VASSAL.app -cp Contents/Resources/Java/Vengine.jar -Xdock:name=World in Flames Final Edition -Xdock:icon=/Applications/VASSAL.app/Contents/Resources/VASSAL.icns -Dapple.awt.graphics.UseQuartz=false VASSAL.launch.Player --load – /Users/Sean/Desktop/8.542.vmod
2017-07-30 10:05:26,654 [1-main] INFO VASSAL.launch.StartUp - Starting
2017-07-30 10:05:26,661 [1-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.10.5
2017-07-30 10:05:26,661 [1-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_121
2017-07-30 10:05:26,662 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2017-07-30 10:05:26,662 [1-main] INFO VASSAL.launch.Launcher - Player
2017-07-30 10:05:29,194 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - VASSAL images folder found at jar:file:/Applications/VASSAL.app/Contents/Resources/Java/Vengine.jar!/images/
2017-07-30 10:05:29,199 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-server created for network-server.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-down created for go-down.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-idle created for network-idle.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL created for VASSAL.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family calculator created for calculator.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-up created for go-up.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL-jabber created for VASSAL-jabber.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family jabber created for jabber.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family bug created for bug.png
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family yes created for yes.svg
2017-07-30 10:05:29,200 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family no created for no.svg

Thus spake peterjfrigate:

Thanks for your reply. I am still struggling to find where the heap
size is too large in the error log:

2017-07-30 10:05:25,957 [0-SwingWorker-pool-1181550434-thread-1] INFO
VASSAL.tools.io.ProcessLauncher - launching /Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Xms64M -Xmx128M
-DVASSAL.id=1 -DVASSAL.port=59107 -Duser.home=/Users/Sean
-Duser.dir=/Applications/VASSAL.app -cp
Contents/Resources/Java/Vengine.jar -Xdock:name=World in Flames Final
Edition
-Xdock:icon=/Applications/VASSAL.app/Contents/Resources/VASSAL.icns
-Dapple.awt.graphics.UseQuartz=false VASSAL.launch.Player --load –
/Users/Sean/Desktop/8.542.vmod

The initial and maximum heap sizes are here: 64MB and 128MB,
respectively. Those are the failsafe values, which are being used
because the values stored in your module preferences file are too large.

This post has instructions for editing the values stored in your module
preferences file:


J.