VASSAL / VASL Freezes

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
Sorry, been busy the last couple of days. Running the test program brings up the TestFileDialog box as shown in the screenshot:
19269
 

uckelman

Senior Member
Joined
Sep 12, 2011
Messages
714
Reaction score
439
Location
Durham
Country
llUnited Kingdom
With 3.6.0-beta3, at what point exactly does Vassal stop responding?
  • Do you get a file dialog after selecting File > Open Module?
  • Are you able to select a file?
  • Are you able to open a module by clicking it in the Module Manager instead?
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
It freezes immediately after selecting File/Open Module. So the answer to all 3 questions is no.
 

uckelman

Senior Member
Joined
Sep 12, 2011
Messages
714
Reaction score
439
Location
Durham
Country
llUnited Kingdom
It freezes immediately after selecting File/Open Module. So the answer to all 3 questions is no.
Regarding this question: "Are you able to open a module by clicking it in the Module Manager instead?"

Are you unable to open a module by clicking on it in the Module Manager because it freezes when you do, or because you have none displayed in the Module Manager?
 

uckelman

Senior Member
Joined
Sep 12, 2011
Messages
714
Reaction score
439
Location
Durham
Country
llUnited Kingdom
Try opening a module with this diagnostic build and paste me back the error log from the run. The error log should show me how far the process of opening the module gets.
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
Sorry, the link to the diagnostic build gave me a 404 error.

Unfortunately, the modules in the Module Manager display box are out of date. So when I try double clicking it, it gives me an out of date error. Then, when I try to open the newer file by using the File/Open Module command, it freezes up entirely.
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
And it still freezes up.

This the latest error log:
2021-10-20 19:26:15,761 [23568-main] INFO VASSAL.launch.StartUp - Starting
2021-10-20 19:26:15,776 [23568-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2021-10-20 19:26:15,776 [23568-main] INFO VASSAL.launch.StartUp - Java version 17
2021-10-20 19:26:15,776 [23568-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.0-SNAPSHOT-8e6f64584\jre
2021-10-20 19:26:15,776 [23568-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.0-SNAPSHOT-8e6f64584
2021-10-20 19:26:16,120 [23568-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-10-20 19:26:51,978 [23568-AWT-EventQueue-0] INFO VASSAL.launch.Player$PromptLaunchAction - 1
 

uckelman

Senior Member
Joined
Sep 12, 2011
Messages
714
Reaction score
439
Location
Durham
Country
llUnited Kingdom

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
I've just tried the 3.6.0-beta4 version. Hangs up again. (I had to take a grandkids break. Too little to do anything with but too cute to ignore.) ;)

The latest error log:
2021-10-27 19:27:10,467 [16292-main] INFO VASSAL.launch.StartUp - Starting
2021-10-27 19:27:10,498 [16292-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2021-10-27 19:27:10,498 [16292-main] INFO VASSAL.launch.StartUp - Java version 17
2021-10-27 19:27:10,498 [16292-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.0-beta4\jre
2021-10-27 19:27:10,498 [16292-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.0-beta4
2021-10-27 19:27:10,748 [16292-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
And version 3.6.0-beta5 hangs up also.

2021-10-27 19:36:59,898 [3324-main] INFO VASSAL.launch.StartUp - Starting
2021-10-27 19:36:59,914 [3324-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2021-10-27 19:36:59,914 [3324-main] INFO VASSAL.launch.StartUp - Java version 17
2021-10-27 19:36:59,914 [3324-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.0-beta5\jre
2021-10-27 19:36:59,914 [3324-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.0-beta5
2021-10-27 19:37:00,164 [3324-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
The second diagnostic build seems to get a little further along than the rest (see below):

2021-11-08 21:30:59,474 [21156-main] INFO VASSAL.launch.StartUp - Starting
2021-11-08 21:30:59,477 [21156-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2021-11-08 21:30:59,477 [21156-main] INFO VASSAL.launch.StartUp - Java version 17
2021-11-08 21:30:59,477 [21156-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.0-SNAPSHOT-739a342c9\jre
2021-11-08 21:30:59,477 [21156-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.0-SNAPSHOT-739a342c9
2021-11-08 21:30:59,742 [21156-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-11-08 21:31:26,964 [21156-AWT-EventQueue-0] INFO VASSAL.launch.Player$PromptLaunchAction - 1
2021-11-08 21:31:26,964 [21156-AWT-EventQueue-0] INFO VASSAL.launch.AbstractLaunchAction - promptForFile 1
2021-11-08 21:31:26,964 [21156-AWT-EventQueue-0] INFO VASSAL.launch.AbstractLaunchAction - promptForFile 2
2021-11-08 21:31:26,964 [21156-AWT-EventQueue-0] INFO VASSAL.launch.AbstractLaunchAction - promptForFile 3


Seriously, I am beginning to think that my OS (Windows 10) doesn't play well with VASSAL.
 

uckelman

Senior Member
Joined
Sep 12, 2011
Messages
714
Reaction score
439
Location
Durham
Country
llUnited Kingdom
The second diagnostic build seems to get a little further along than the rest
It doesn't, nor is it intended to. What it's doing is producing more output along the execution path. This is how I'm tracing what hangs. We should be able to identify a single line of code after a few more iterations.

Now we know that FileChooser.showOpenDialog() isn't returning; the third diagnostic build will show what inside that gets stuck.

Seriously, I am beginning to think that my OS (Windows 10) doesn't play well with VASSAL.
Thousands of people use Windows 10 with Vassal every day without a problem. The trigger for the problem is likely something unusual about your machine.

Here's the third diagnostic build. Run it like the previous two and post the error log.
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
It doesn't, nor is it intended to. What it's doing is producing more output along the execution path. This is how I'm tracing what hangs. We should be able to identify a single line of code after a few more iterations.

Now we know that FileChooser.showOpenDialog() isn't returning; the third diagnostic build will show what inside that gets stuck.


Thousands of people use Windows 10 with Vassal every day without a problem. The trigger for the problem is likely something unusual about your machine.

Here's the third diagnostic build. Run it like the previous two and post the error log.
I want to thank everyone for your help in trying to solve this very perplexing problem. The key to the solution was actually in my machine itself and you nailed it with the "trigger in my machine" phrase above.

My desktop, while quite good otherwise, is getting old and was very slow to load up when powered on. Once on, it seemed to work perfectly except for the VASL freezing problem, which began shortly after my OS was upgraded to Windows 10. So, this led me to believe that the problem was a VASSAL / Windows 10 conflict. It was driving me batty. I had put off trying to solve the problem for a long time since I was extremely busy (working two jobs at the time) and didn't have any time for it. Now that I'm back to only one job (THANK GOD!!!), I wanted to get back to VASL and was trying to solve the freeze up problem. This was when I finally turned to the community to try to figure this out.

After several tests were tried and kept getting the same problem, I was about to give up on ever finding a solution when my old, slow desktop finally gave up and the whole thing crashed on me. It has taken over a month to get it fixed (mainly due to the perpetual not enough money to go around problem that still hasn't been solved). So, after putting in a brand new speedy SSD drive, the old desktop not only boots up much faster (it is almost like a new computer now :giggle:), lo and behold the VASL freezing problem has vanished!! I can open up the latest VASL 6.6.3.1 on VASSAL 3.6.4 without any problem. I've been testing it for a week now just to be sure that it is not too good to be true. Thank you, thank you, thank you.
 

DougRim

Forum Guru
Joined
Apr 23, 2012
Messages
1,957
Reaction score
2,234
Location
Ottawa
Country
llCanada
Huge kudos to uckelman who did some extraordinary work here to support VASL users!!!! We owe ya!
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
What was so perplexing about it was that VASL was the only program that I was having a problem with. Everything else worked fine, even if it was really slow. My only explanation is that as my hard drive was getting old it was starting to deteriorate. Since VASL is my most heavily used program other than the web browser, it was just my luck that the drive started to wear out where the VASL/VASSAL files are stored first. First time I tried it after getting the new SSD drive installed it opened up VASL/VASSAL instantly. Works like a charm now. My only problem now is figuring out all the new bells and whistles that have been added since I've been locked out. ;)👍
 

Brave Lion

Member
Joined
May 31, 2005
Messages
126
Reaction score
43
Location
Tacoma
Country
llUnited States
I had the tech wizards at Best Buy work their magic on it, so I'm not sure if a Windows reinstall was part of the process. But I'm guessing that it probably was. I've had to reinstall all of my apps since bringing my computer back home from the hospital.
 
Top