I am having a serious problem with the latest vassal version (v24). I edit the module. I have an at-start stack under “Main Map” that I want to reposition. I press that button and open that window. I cannot drag the piece for an unknown reason. When I click ok, it hangs for about 20 seconds. Then the editor crashes and disappears. I have tried this too with v23. Same result. This is leaving me dead in the water.
More precise instructions: Edit module. Open Main Map. Go to the last element, a folder named Dice. It contains one piece, a red die, at (100,100). Try repositioning the at-start stack.
Yes. There’s a piece there. A couple things I forgot. First, a residual app hangs onto the vmod, so I must reboot to try again. Second, I think it fails if I try to reposition any piece, not just the new one. I wondering if adding the piece pushed me over a memory boundary. I check that when I get home.
2026-07-24 13:27:28,563 [21656-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "TimerQueue"
2026-07-24 13:27:54,725 [21656-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream -
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "AWT-Windows"
The immediate problem you’re seeing based on the error log is running out of memory. I can’t replicate the problem myself from your instructions.
Aside: You have the wrong button text for the Ginger window.
You shouldn’t need to reboot the machine completely. It should be enough to kill the Vassal Module Manager, which is the one that holds on to the file. The editor process dies completely and does not hold a lock - or at least shouldn’t.
I cannot reproduce the problem (either - mine and @uckelman’s post crossed) on Linux.
The immediate problem you’re seeing based on the error log is running out of memory. I can’t replicate the problem myself from your instructions.
Aside: You have the wrong button text for the Ginger window.
I just got home, tested it with more memory, and it worked. Problem solved. This is the first time I’ve run into a memory barrier. I’m embarrassed that I didn’t spot the message in the error log though. I should know better.
Yes, I see I misnamed a window. This vmod is in the very early stages of coming together, so I expect I will find mistakes. I haven’t started wiring it for functionality.
When I exited all Vassal s/w including the main vassal controller and restarted it, I still couldn’t save or edit the mod because something still had it open. It was either reboot or search through the task manager and kill the suspects. I suspected it was a java app, not a vassal one, that still had it hands on it.