Trouble running Streets of Stalingrad module

I’m getting a “Out of Memory” message that directs me to “increase max heap size” in the Preferences. I tried that, and then rebooted VASSAL. No Joy. I’ve got nearly 27 Gb available on the hard drive.

Any suggestions?

Thus spake Climberat:

I’m getting a “Out of Memory” message that directs me to “increase max
heap size” in the Preferences. I tried that, and then rebooted VASSAL.
No Joy. I’ve got nearly 27 Gb available on the hard drive.

Any suggestions?

What did you have for max heap? To what did you change it?

Heap size has nothing to do with your hard disk, btw. It’s the amount of
RAM that Java will let VASSAL use.


J.

I raised it from 512 to 1024 as recommended by the module write up. That didn’t work, so I raised it to 2048. Still nothing.

Thus spake Climberat:

I raised it from 512 to 1024 as recommended by the module write up.
That didn’t work, so I raised it to 2048. Still nothing.

In what way did changing the max heap to 1024 not work?

J.

Hey uckelman,

Thanks for the replies.

I’m still getting the same “Out of Memory” message. It’s as if changing the increasing the max heap size did nothing. All other modules run fine.

Thus spake Climberat:

Hey uckelman,

Thanks for the replies.

I’m still getting the same “Out of Memory” message. It’s as if changing
the increasing the max heap size did nothing. All other modules run
fine.

  1. How much RAM does your machine have?

  2. Please send the errorLog from immediately after a run in which you’ve
    had an “Out of Memory” message. (You can find the errorLog via the Help
    menu of the Module Manager.)


J.

RAM: 4 GB 667 MHz DDR2 SDRAM

Note: I’m running it on a MacBook Pro. I have another, newer MacBook Pro with 8 GB 1600 MHz DDR3, same issue. Also, I did get the “Processing Image Tiles” window open up prior to attempting to run it.

Error Log:
2014-09-04 22:39:16,991 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-09-04 22:39:16,997 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.7.5
2014-09-04 22:39:16,997 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_65
2014-09-04 22:39:16,997 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.13
2014-09-04 22:39:18,358 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-09-04 22:39:28,968 [0-SwingWorker-pool-459973678-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file /Users/climberat/Dave’s Personal/Games/VASSAL/Modules/SoS_Scenarios_1-3v02.vmod
2014-09-04 22:39:29,560 [0-SwingWorker-pool-459973678-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2014-09-04 22:39:29,561 [0-SwingWorker-pool-459973678-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module Scenarios 1-3
2014-09-04 22:39:29,564 [0-SwingWorker-pool-459973678-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java -Xms256M -Xmx512M -DVASSAL.id=1 -DVASSAL.port=52008 -Duser.home=/Users/climberat -cp Contents/Resources/Java/Vengine.jar -Xdock:name=Scenarios 1-3 -Xdock:icon=/Applications/VASSAL.app/Contents/Resources/VASSAL.icns -Dapple.awt.graphics.UseQuartz=false VASSAL.launch.Player --load – /Users/climberat/Dave’s Personal/Games/VASSAL/Modules/SoS_Scenarios_1-3v02.vmod
2014-09-04 22:39:30,710 [1-main] INFO VASSAL.launch.StartUp - Starting
2014-09-04 22:39:30,724 [1-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.7.5
2014-09-04 22:39:30,724 [1-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_65
2014-09-04 22:39:30,724 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.13
2014-09-04 22:39:30,724 [1-main] INFO VASSAL.launch.Launcher - Player
2014-09-04 22:39:33,713 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - VASSAL images folder found at jar:file:/Applications/VASSAL.app/Contents/Resources/Java/Vengine.jar!/images/
2014-09-04 22:39:33,767 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-server created for network-server.png
2014-09-04 22:39:33,767 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-down created for go-down.png
2014-09-04 22:39:33,767 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-idle created for network-idle.png
2014-09-04 22:39:33,767 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL created for VASSAL.png
2014-09-04 22:39:33,767 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family calculator created for calculator.png
2014-09-04 22:39:33,768 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-up created for go-up.png
2014-09-04 22:39:33,768 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL-jabber created for VASSAL-jabber.png
2014-09-04 22:39:33,768 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family jabber created for jabber.png
2014-09-04 22:39:33,768 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family bug created for bug.png
2014-09-04 22:39:33,769 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family yes created for yes.svg
2014-09-04 22:39:33,769 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family no created for no.svg
2014-09-04 22:39:46,715 [1-AWT-EventQueue-0] WARN VASSAL.launch.BasicModule - Scenarios 1-3 version 0.2
2014-09-04 22:41:14,902 [1-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog -
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882) ~[na:1.6.0_65]
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) ~[na:1.6.0_65]
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390) ~[na:1.6.0_65]
at java.lang.StringBuilder.append(StringBuilder.java:119) ~[na:1.6.0_65]
at VASSAL.tools.SequenceEncoder.appendEscapedString(SequenceEncoder.java:149) ~[Vengine.jar:na]
at VASSAL.tools.SequenceEncoder.append(SequenceEncoder.java:88) ~[Vengine.jar:na]
at VASSAL.launch.BasicModule.encode(BasicModule.java:252) ~[Vengine.jar:na]
at VASSAL.launch.BasicModule.encode(BasicModule.java:250) ~[Vengine.jar:na]
at VASSAL.build.module.GameState.saveString(GameState.java:417) ~[Vengine.jar:na]
at VASSAL.build.module.GameState.setup(GameState.java:312) ~[Vengine.jar:na]
at VASSAL.build.module.WizardSupport.showWelcomeWizard(WizardSupport.java:205) ~[Vengine.jar:na]
at VASSAL.launch.Player.launch(Player.java:92) ~[Vengine.jar:na]
at VASSAL.launch.Launcher$1.run(Launcher.java:149) ~[Vengine.jar:na]
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) ~[na:1.6.0_65]
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:715) ~[na:1.6.0_65]
at java.awt.EventQueue.access$400(EventQueue.java:82) ~[na:1.6.0_65]
at java.awt.EventQueue$2.run(EventQueue.java:676) ~[na:1.6.0_65]
at java.awt.EventQueue$2.run(EventQueue.java:674) ~[na:1.6.0_65]
at java.security.AccessController.doPrivileged(Native Method) ~[na:1.6.0_65]
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:86) ~[na:1.6.0_65]
at java.awt.EventQueue.dispatchEvent(EventQueue.java:685) ~[na:1.6.0_65]
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296) [na:1.6.0_65]
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211) [na:1.6.0_65]
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201) [na:1.6.0_65]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196) [na:1.6.0_65]
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188) [na:1.6.0_65]
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) [na:1.6.0_65]

Thus spake Climberat:

RAM: 4 GB 667 MHz DDR2 SDRAM

Note: I’m running it on a MacBook Pro. I have another, newer MacBook
Pro with 8 GB 1600 MHz DDR3, same issue. Also, I did get the
“Processing Image Tiles” window open up prior to attempting to run it.

Increase your maximum heap size for the module. (Look on the General
tab in Preferences for the module.)


J.

Hey uckelman!

That did it!!

Thank you SO much for your help! I was really getting frustrated, as I was really looking forward to playing this game on VASSAL.