Vassal 3.2.2 won't exit

Technical Support & Bugs
1

Vassal 3.2.2 won’t exit on Windows 7, 64-bit system. After opening a module, then choosing Quit from the File menu of the module, the drop-down boxes freeze and the application becomes non-responsive. Minimizing the Control and restoring results in a black window inside the frame.

Choosing Quit from the Control will close the module successfully, but leave the Control non-responsive.

2

Thus spake Hagar:

Vassal 3.2.2 won’t exit on Windows 7, 64-bit system. After opening a
module, then choosing Quit from the File menu of the module, the
drop-down boxes freeze and the application becomes non-responsive.
Minimizing the Control and restoring results in a black window inside
the frame.

Choosing Quit from the Control will close the module successfully, but
leave the Control non-responsive.

Please post the contents of the errorLog. You’ll find it in
C:\Users\yourusername\AppData\Roaming\VASSAL.

–
J.

3

I’ve had this happen if there’s not enough memory allocated to the Vassal module that’s running. You can hard close it by going to your task manager and closing process java.exe.

4
  1. I did use the Task Manager to kill it when necessary.
  2. I can’t reliably cause it to happen (and thus delayed posting).
  3. I can eventually get it to happen, but by that time, I’ve tried so many things, I can’t remember the final sequence that caused it.
    I’ve included errorLog when it finally happened. Won’t accept the file. Included text.
  4. If I can identify the sequence, I’ll post it.

errorLog text:

2013-02-11 21:19:00,619 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-02-11 21:19:00,619 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7
2013-02-11 21:19:00,619 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_37
2013-02-11 21:19:00,619 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.2
2013-02-11 21:19:00,665 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2013-02-11 21:19:06,734 [0-SwingWorker-pool-1222269888-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Games\Crete\Crete_v104.2.vmod
2013-02-11 21:19:06,859 [0-SwingWorker-pool-1222269888-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2013-02-11 21:19:06,859 [0-SwingWorker-pool-1222269888-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module Crete
2013-02-11 21:19:06,859 [0-SwingWorker-pool-1222269888-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\Java\jre6\bin\java -Xms256M -Xmx512M -DVASSAL.id=1 -DVASSAL.port=49517 -Duser.home=C:\Users\office -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Games\Crete\Crete_v104.2.vmod
2013-02-11 21:19:07,311 [1-main] INFO VASSAL.launch.StartUp - Starting
2013-02-11 21:19:07,311 [1-main] INFO VASSAL.launch.StartUp - OS Windows 7
2013-02-11 21:19:07,311 [1-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_37
2013-02-11 21:19:07,311 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.2
2013-02-11 21:19:07,311 [1-main] INFO VASSAL.launch.Launcher - Player
2013-02-11 21:19:09,043 [1-AWT-EventQueue-0] WARN VASSAL.launch.BasicModule - Crete version 1.0.4.2
2013-02-11 21:19:32,318 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting

5

Joel,
This is one of my GTS modules which are all hanging on exit due to the Zip file being locked.

Hagar,
This is a known problem, you can get around it by using vassal 3.1 for now, or just by force closing vassal from the Task manager.

Regards,
Brent,

6

Thus spake Brent Easton:

Joel,
This is one of my GTS modules which are all hanging on exit due to the
Zip file being locked.

Ok. I haven’t had time to get back to that. I will, but it might not
be until March.

–
J.

7

OK.

Thanks for the info.