B4J Question Serial Port issue with OpenJDK [SOLVED]

[Didier9]

I thought that issue was resolved. It is described in this post:

Updated JSSC.Jar

I fixed and recompiled the Native DLL for JSSC which was causing Access Violation crashes when attempting to open a serial port on Windows 10 64 bit systems with newer Java versions. With Java 8 x64, it was hit and miss. One system crashed while another did not. x32 always worked of course...

www.b4x.com

I just got a new laptop and I had to reinstall everything. I am getting the dreaded EXCEPTION_ACCESS_VIOLATION with the OpenJDK I just downloaded from this site:

Waiting for debugger to connect...
Program started.
COM3
COM4
COM5
COM6
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000007110b5db, pid=17128, tid=22284
#
# JRE version: OpenJDK Runtime Environment (11.0.1+13) (build 11.0.1+13)
# Java VM: OpenJDK 64-Bit Server VM (11.0.1+13, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# C  [jSSC-2.8_x86_64.dll+0xb5db]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\jugesd\ONEDRI~1\DOCUME~1\B4JPRO~1\CAN232~1\dev\Objects\hs_err_pid17128.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

I know I had resolved this, with help from the forum but I can't find the link.

This is under Windows 10 64 bits.

Any help appreciated

 

[Didier9]

Now that I think of it, I believe I had resolved it by using the Oracle JDK... I need to access my old machine if it has not been recycled yet...

 

[bdunkleysmith]

These two references may be of assistance: jSerial and B4J Packager 11 and Tips and special cases 5.

 

[OliverA]

Now that I think of it, I believe I had resolved it by using the Oracle JDK.

Did you happen to also do this? https://www.b4x.com/android/forum/threads/updated-jssc-jar.99668/post-670761

 

[OliverA]

Actually, looks like you need to re-update the jssc library after a fresh install. See https://www.b4x.com/android/forum/threads/problem-with-new-install.107611/post-673049

 

[bdunkleysmith]

Did you happen to also do this? https://www.b4x.com/android/forum/threads/updated-jssc-jar.99668/post-670761

After trying that fix and a few others found in the Forum with variable success, I found following the guidance of @Erel in the two references I cited above fixed the problem reliably.

 

[Didier9]

Thank you, I'll go over those. Seems like I need to educate myself with the integrated B4J Packager. I have not used it yet

 

[Didier9]

Just a question, since the new library is "linked" after a package is created, how does it work during debug?

 

[Didier9]

This actually was the fix:

https://www.b4x.com/android/forum/threads/updated-jssc-jar.99668/

1) Copy the modified jssc.jar file to the Library folder, and
2) Delete the .jssc folder in your home directory (C:\User\<your login>)