Not a B4J issue proper, but an issue using it nevertheless...
I installed B4J with OpenJDK11.
I an getting this error when trying to open a COM port under Win 10 64:
I googled it and found a number of references to this bug being due to an issue with the jssc library (as pointed out by the error log).
I switched to the Oracle version of Java and the problem went away.
It seems strange (and more than a little bit disappointing) that this particular issue has been reported for quite some time and that nobody has fixed it.
I installed B4J with OpenJDK11.
I an getting this error when trying to open a COM port under Win 10 64:
B4X:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006a00b5bb, pid=3152, tid=5668
#
# 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.6_x86_64.dll+0xb5bb]
#
# 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\Owner\DOCUME~1\B4JPRO~1\R9_B4J\dev\Objects\hs_err_pid3152.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 googled it and found a number of references to this bug being due to an issue with the jssc library (as pointed out by the error log).
I switched to the Oracle version of Java and the problem went away.
It seems strange (and more than a little bit disappointing) that this particular issue has been reported for quite some time and that nobody has fixed it.