VASL "eeek a bug" crash (with 3.2.17)

Technical Support & Bugs
1

back here, after so many years, and this speak volumes about the stability of VASSAL.

The issue I have now regards VASL, and seems to me not related to the known 3.3/4.x issues.

I have, with VASSAL 3.2.17 a crash with VASL 6.5.1, but the “EEEK a bug” window don’t allow a copy-paste of the detailed error report (!!!). Perhaps this also is a bug :laughing:

I use java-11-openjdk-amd64 under Linux.

Best regards from Italy,
dott. Piergiorgio.

2

VASSAL 3.2.17 isn’t compatible with Java 11. You’ll either need to install Java 8 or wait for a new release of VASL which is compatible with VASSAL 3.3+.

3

Thus spake Piergiorgio:

I use java-11-openjdk-amd64 under Linux.

If you’re using Java 11, that’s your problem. VASSAL 3.2.17 cannot be
used with anything later than Java 8.

We expect a VASL release soon which is compatible with VASSAL 3.4, as
the VASL devs are no longer waiting on us for a release.

–
J.

4

uh ? seems strange to me, because all three currently installed VASSALs works fine…

this environment is Debian, and I have both 8 and 11, plus a legacy one, kept for reasons not involving VASSAL:

$ update-alternatives --list java
/usr/bin/gij-6
/usr/lib/jvm/java-11-openjdk-amd64/bin/java
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java

and 3.2.17 run fine under java 11, aside that since I started 3.3.2 and later 3.4.1 there’s a nagging “update available” warning message; only error messages, on the Linux command line (that is, stderr):

VASSAL-3.2.17$ ./VASSAL.sh 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by VASSAL.tools.image.ImageIOImageLoader (file:/home/pigi/opt/vassal/VASSAL-3.2.17/lib/Vengine.jar) to field sun.java2d.cmm.ProfileDeferralMgr.deferring
WARNING: Please consider reporting this to the maintainers of VASSAL.tools.image.ImageIOImageLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

3.3.2 and 3.4.1 don’t show the error message and of course 3.4.1 don’t show the update available nag (will be nice if can be disabled when using non-current Vassal for running non upward compatible modules…)

as the first quote above, I use update-alternatives, whose currently are pointing to java 11:

$ update-alternatives --config java
Sono disponibili 3 scelte per l'alternativa java (che fornisce /usr/bin/java).

  Selezione    Percorso                                        Priorità  Stato
------------------------------------------------------------
* 0            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      modalità automatica
  1            /usr/bin/gij-6                                   1060      modalità manuale
  2            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      modalità manuale
  3            /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java   1081      modalità manuale

Premere Invio per mantenere il valore predefinito[*] o digitare il numero della selezione:

:bulb: if I edit 3.2.17 VASSAL.sh, pointing it directly to java 8 ? as noticeable above, should be a very simple one, pasting /usr/lib/jvm/java-8… prior of java -Duser… in the last line. Your opinions ?

Best regards from Italy,
dott. Piergiorgio.

5

Thus spake Piergiorgio:

and 3.2.17 run fine under java 11,

Check your errorLog when you’re running 3.2.17 successfully. That will tell
you which verison of Java it’s running with. It won’t be Java 11.

aside that since I started 3.3.2 and
later 3.4.1 there’s a nagging “update available” warning message; only
error messages, on the Linux command line (that is, stderr):

Code:

VASSAL-3.2.17$ ./VASSAL.sh
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
VASSAL.tools.image.ImageIOImageLoader
(file:/home/pigi/opt/vassal/VASSAL-3.2.17/lib/Vengine.jar) to field
sun.java2d.cmm.ProfileDeferralMgr.deferring
WARNING: Please consider reporting this to the maintainers of
VASSAL.tools.image.ImageIOImageLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future
release

Yes, this is what you’re going to see when you try running 3.2.17
with Java 11—it won’t work.

3.3.2 and 3.4.1 don’t show the error message

They wouldn’t, because they work with Java 11.

:idea: if I edit 3.2.17 VASSAL.sh, pointing it directly to java 8 ? as
noticeable above, should be a very simple one, pasting
/usr/lib/jvm/java-8… prior of java -Duser… in the last line. Your
opinions ?

That should work. It’s how I run 3.2.17 locally when I need to check
something.

–
J.

6

Indeed has worked. Issue solved, I suppose ?

Thanks, and good work !

Best regards from Italy,
dott. Piergiorgio.