Vassal 3.2.8 CTD's 20 seconds after opening

Technical Support & Bugs
#1

Hi, Just downloaded and installed Vassal without any obvious issues, and now 20 seconds after load vassal crashes

Model: Home Built
Operating System: Windows 7 Ultimate 64bit
CPU: AMD Phenom 2 x4 955 3.2GHz
Memory 8GB
Video Card: Geforce GTX 295
Vassal version. :3.2.8
Java version. 7 Update 45 32 and 64bit versions
Vassal module name and version: N/A

Reproducing the problem:
Run Vassal, wait roughly 20 seconds, crash to desktop, no error message present, no log file in folder, log file from help menu prior to crash shows:
2013-12-16 21:58:15,935 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_45
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.8
2013-12-16 21:58:15,991 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager

I have not yet downloaded any modules, when I select new module, I just get the windows spinning busy cursor until the 20 seconds is up and vassal crashes.

I’ve restarted my computer and reduced everything else running to just Avast (nothing appears in Avast’s logs while accessing Vassal) and the crash is still present.

Any more information needed? Any help would be appreciated.

I’ve had vassal recommended to me by a few friends (who use other OS’s) and I’ve offered to build a module for Full Thrust… not turning out so well so far - spent a weekend reading the documentation, got back to my PC, installed it and this occurred - Joy.

#2

Thus spake EdTheRabbit:

Hi, Just downloaded and installed Vassal without any obvious issues, and
now 20 seconds after load vassal crashes

Model: Home Built
Operating System: Windows 7 Ultimate 64bit
CPU: AMD Phenom 2 x4 955 3.2GHz
Memory 8GB
Video Card: Geforce GTX 295
Vassal version. :3.2.8
Java version. 7 Update 45 32 and 64bit versions
Vassal module name and version: N/A

Reproducing the problem:
Run Vassal, wait roughly 20 seconds, crash to desktop, no error message
present, no log file in folder, log file from help menu prior to crash
shows:
2013-12-16 21:58:15,935 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - OS
Windows 7 6.1
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - Java
version 1.7.0_45
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.8
2013-12-16 21:58:15,991 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManager - Manager

We need the error log from after the crash. Look here for how to find it:

vassalengine.org/wiki/Error_Logs

–
J.

#3

Thanks for the link - ErrorLog as follows:

2013-12-16 21:58:15,935 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_45
2013-12-16 21:58:15,939 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.8
2013-12-16 21:58:15,991 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2013-12-16 21:58:37,312 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 53670
2013-12-16 21:58:37,313 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,314 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.ConnectException: Connection timed out: connect
2013-12-16 21:58:37,314 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,314 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2013-12-16 21:58:37,315 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,315 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2013-12-16 21:58:37,315 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,316 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2013-12-16 21:58:37,316 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,316 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2013-12-16 21:58:37,317 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,317 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2013-12-16 21:58:37,317 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,317 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2013-12-16 21:58:37,318 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,318 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2013-12-16 21:58:37,318 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,319 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2013-12-16 21:58:37,319 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,320 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2013-12-16 21:58:37,320 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,320 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2013-12-16 21:58:37,321 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,321 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2013-12-16 21:58:37,321 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2013-12-16 21:58:37,322 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2013-12-16 21:58:37,322 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

#4

There was a similar situation on the Consimworld forum recently where an Avast user could not launch VASSAL and was getting these same kinds of things in his errorlog. It appears that Avast is overly aggressive at blocking Java programs of all kinds, as evident on the Avast site’s forums.

It may not be a solution that works for you, but this other user having the identical problem switched to a different firewall product (or turned it off completely, I can’t recall which), and VASSAL worked just fine again.

#5

Avast released a new software version for 2014, but it is (was) incompatible with Vassal. Every time Vassal started, it would disappear (time out) after 20 seconds or so. It failed trying to connect to a port. I had to shut down the avast firewall every time I ran Vassal.

But good news! Avast released a new update on 12/17/2013 that fixes the problem! From within avast, you should be able to manually update the software. It works for me.