Vassal 3.6.2 freezes

Technical Support & Bugs
1

Did not have this problem with the last version I was using (3.4.6).

On occasion when playing via the server I press the 2D6 button and my opponent sees the roll but my game freezes up and I have to exit using the Task Manager. The module we are using is named in the error log I have included. This problem is very intermittent, but also very annoying.

I updated my Java and although seemingly less often, it still occurs. Here’s the error log contents. The problem occurred at 12:56.

==================================================================
2022-02-27 11:52:52,946 [15692-main] INFO VASSAL.launch.StartUp - Starting
2022-02-27 11:52:52,962 [15692-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-02-27 11:52:52,962 [15692-main] INFO VASSAL.launch.StartUp - Java version 17.0.1
2022-02-27 11:52:52,966 [15692-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.2\jre
2022-02-27 11:52:52,966 [15692-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.2
2022-02-27 11:52:53,286 [15692-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2022-02-27 11:53:05,728 [15692-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file D:\Games\Vassal\Fstr_0_94.vmod
2022-02-27 11:53:07,171 [15692-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2022-02-27 11:53:07,174 [15692-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module From Salerno To Rome
2022-02-27 11:53:07,184 [15692-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.6.2\jre\bin\java -Xms512M -Xmx512M -Duser.home=C:\Users\Paul -Duser.dir=C:\Program Files\VASSAL-3.6.2 -cp lib\Vengine.jar VASSAL.launch.Player --load – D:\Games\Vassal\Fstr_0_94.vmod
2022-02-27 11:53:08,558 [16144-main] INFO VASSAL.launch.StartUp - Starting
2022-02-27 11:53:08,573 [16144-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-02-27 11:53:08,573 [16144-main] INFO VASSAL.launch.StartUp - Java version 17.0.1
2022-02-27 11:53:08,574 [16144-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.2\jre
2022-02-27 11:53:08,574 [16144-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.2
2022-02-27 11:53:08,574 [16144-main] INFO VASSAL.launch.Launcher - Player
2022-02-27 11:53:12,027 [16144-AWT-EventQueue-0] INFO VASSAL.build.GameModule - From Salerno To Rome version 0.94
2022-02-27 11:53:19,193 [16144-AWT-EventQueue-0] INFO VASSAL.build.module.GameState - Loading save game D:\Games\Vassal\FSTR Saved Games\Start 1.3.vsav, created with module version 0.94
2022-02-27 11:55:38,632 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:02:26,054 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:04:26,066 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:11:41,058 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:13:41,061 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:15:41,076 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:22:47,307 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:24:55,830 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:35:03,350 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:42:47,548 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:49:45,768 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:51:45,781 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:53:45,793 [16144-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-02-27 12:57:34,554 [15692-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

2

Updating Java will do nothing if you’re using the Windows package—it uses the Java bundled with it.

3.6.2 isn’t current. Does the problem occur with 3.6.5?

3

Will update and let you know.

4

I updated to 3.6.5 but had two more freezes today. My online opponent has not had any of these.

On the first one at 13:00, I was dragging a unit across the screen when it froze. Here is the log:

======================================================================
2022-03-06 11:50:42,472 [14604-main] INFO VASSAL.launch.StartUp - Starting
2022-03-06 11:50:42,488 [14604-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-03-06 11:50:42,488 [14604-main] INFO VASSAL.launch.StartUp - Java version 17.0.2
2022-03-06 11:50:42,488 [14604-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.5\jre
2022-03-06 11:50:42,488 [14604-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.5
2022-03-06 11:50:42,781 [14604-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2022-03-06 11:51:02,681 [14604-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file D:\Games\Vassal\Fstr_0_94.vmod
2022-03-06 11:51:04,200 [14604-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2022-03-06 11:51:04,204 [14604-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module From Salerno To Rome
2022-03-06 11:51:04,212 [14604-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.6.5\jre\bin\java -Xms512M -Xmx512M -Duser.home=C:\Users\Paul -Duser.dir=C:\Program Files\VASSAL-3.6.5 -cp lib\Vengine.jar VASSAL.launch.Player --load – D:\Games\Vassal\Fstr_0_94.vmod
2022-03-06 11:51:05,279 [15528-main] INFO VASSAL.launch.StartUp - Starting
2022-03-06 11:51:05,295 [15528-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-03-06 11:51:05,295 [15528-main] INFO VASSAL.launch.StartUp - Java version 17.0.2
2022-03-06 11:51:05,295 [15528-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.5\jre
2022-03-06 11:51:05,295 [15528-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.5
2022-03-06 11:51:05,295 [15528-main] INFO VASSAL.launch.Launcher - Player
2022-03-06 11:51:08,915 [15528-AWT-EventQueue-0] INFO VASSAL.build.GameModule - From Salerno To Rome version 0.94
2022-03-06 11:51:46,874 [15528-AWT-EventQueue-0] INFO VASSAL.build.module.GameState - Loading save game D:\Games\Vassal\FSTR Saved Games\Allies 2.3 East is done.vsav, created with module version 0.94
2022-03-06 11:54:13,785 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 11:56:13,801 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 11:58:13,817 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:00:13,818 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:02:41,159 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:05:31,939 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:08:34,635 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:16:36,895 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:20:48,833 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:22:48,847 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:25:22,329 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:27:28,375 [15528-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Source: Layer=-1 Error: Rangers [Layer - END OP overlay.png] . Attempt to select Layer greater than the number of available levels. Turn on the Audit Trail preference to generate more details in the errorlog.
2022-03-06 12:46:26,327 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 12:51:56,677 [15528-write game.vassalengine.org/109.237.26.25] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

2022-03-06 13:02:34,603 [14604-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

====================================================================

For the second one at 13:38, I had clicked on the 2D6 button, my opponent saw the result narrative but Vassal on my computer froze again. Here is that log:

====================================================================
2022-03-06 13:02:50,134 [14392-main] INFO VASSAL.launch.StartUp - Starting
2022-03-06 13:02:50,153 [14392-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-03-06 13:02:50,153 [14392-main] INFO VASSAL.launch.StartUp - Java version 17.0.2
2022-03-06 13:02:50,153 [14392-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.5\jre
2022-03-06 13:02:50,154 [14392-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.5
2022-03-06 13:02:50,450 [14392-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2022-03-06 13:02:55,466 [14392-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file D:\Games\Vassal\Fstr_0_94.vmod
2022-03-06 13:02:55,993 [14392-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2022-03-06 13:02:55,995 [14392-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module From Salerno To Rome
2022-03-06 13:02:56,002 [14392-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.6.5\jre\bin\java -Xms512M -Xmx512M -Duser.home=C:\Users\Paul -Duser.dir=C:\Program Files\VASSAL-3.6.5 -cp lib\Vengine.jar VASSAL.launch.Player --load – D:\Games\Vassal\Fstr_0_94.vmod
2022-03-06 13:02:57,059 [7220-main] INFO VASSAL.launch.StartUp - Starting
2022-03-06 13:02:57,073 [7220-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-03-06 13:02:57,073 [7220-main] INFO VASSAL.launch.StartUp - Java version 17.0.2
2022-03-06 13:02:57,074 [7220-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.5\jre
2022-03-06 13:02:57,074 [7220-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.5
2022-03-06 13:02:57,074 [7220-main] INFO VASSAL.launch.Launcher - Player
2022-03-06 13:03:00,499 [7220-AWT-EventQueue-0] INFO VASSAL.build.GameModule - From Salerno To Rome version 0.94
2022-03-06 13:39:26,695 [14392-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

====================================================================

Is there a deeper logging level I can enable? As you can see the last log shows nothing.

5

You have all the logging there is.

Does the problem happen with only this one module?

6

I will have to try some other modules, I guess. So far this is the only one.

There is one error message in the first of today’s logs, to do with resetting to a layer level. That was one of my edits to the module and I’m unsure if that is the cause. The idea was to have a global command to remove an overlay level by applying it to all units belonging to a prototype, whether or not the layer had been activated up to that point. I am unsure of the documentation on that, as I am resetting to level zero. The strange thing is that there are 6 scenarios and that error message only seems to appear with some of them. Also my opponent has the same module and does not have this problem.

7

Was this ever resolved? I too have issues with Vassal “freezing” for good when I am hovering a counter over the map. Happens all the time with me on Blitzkrieg Legend. Tried a few things like re installing vassal, using an earlier version, earlier module, nothing has fixed it.

8

Does this happen with the current version of Vassal, which is 3.6.7 presently? What version of the TBL module is it? Is there anything in the errorLog? Can you reliably reproduce the problem, and if so, what are the steps for doing so?

9

Yes the current version, and older versions, and the last 4 versions of the module. I have tried many times. It happens - eventually, when I am moving a counter. Could happen 5 mins in, or two hours in. I have to save my game every few minutes to ensure I don’t lose out. It freezes and then I have to close vassal down completely and restart. I have left it for hours to see if it clears and nothing.

10

What’s the current version of the module?

It would also be helpful to see the contents of an errorLog from a run where the problem occurs.

11

I don’t get any other messages but the vassal module freezes and it says “not responding” in the pop ups.
Can’t even stop it by pressing on the X, I have to end it as a process. Completely frozen.
I have tried the last three modules for sure, all the same problem, but have likely even tried older ones years back as I remember it just would never seem to work for me without freezing mid turn.
It’s even frozen on me during the set up phase, but always when I am moving a counter around the map. Not rolling or pulling up charts.

12

What’s the current version of the module? I have no way of knowing what version you think is current.

You can find the errorLog from a run after a crash in the directory where errorLogs are written. See here for the location appropriate for your OS.

13

The problem continued for me after I installed 3.6.5. I was asked to try a different module but have not been playing since finishing the last game we had so I don’t know if that would make a difference.

For me, I typically have the map on my primary (left) side monitor and I move the game charts and tables onto my right hand monitor. Although the problem occurred a few times when moving a counter, for me it happened much more often in two other cases (about equal frequency). These were:
a) clicking the 2D6 button in the module, and
b) moving or resizing or bringing to the front one of the charts.

There was no way I found to “make” it happen. It was random. Sometimes I could play for 2 hours and not have it. Other times it would occur twice within a half hour. The saving grace for us was that my friend and I played on the server so all I had to do was task manager out of Vassal, restart it and then sync up to my friend again. He did not run into this problem even though we were using the same module. We found out after there were times his Vassal was one version behind miine, the same other times and one version ahead still other times. This did not seem to make any difference to the random nature of the problem occurring on my computer. It happened to me with both 3.6.2 and 3.6.5. I have not yet upgraded beyond 3.6.5.

I believe I included error logs in my earlier posts.

14

When you’re using the current release of Vassal and have the problem, let us know and post an error log.