The .cfg file only has mainclass and classpath info, no JVM options.
When running from the application image folder (the one with app and runtime sub-folders) with the command line:
runtime\bin\java.exe -cp app\libs\* mainclassname
the application launches and runs as expected.
Launching via the application .exe file produces the crash report attached.
The JRE image was created with:
jlink.exe --no-header-files --no-man-pages --compress=2 --add-modules javafx.controls,javafx.fxml,java.prefs,java.logging,java.management,jdk.jdwp.agent --output C:\dev\MyApp\build\image\runtime
jpackage used the following command line:
jpackage.exe --type app-image --verbose --temp C:\dev\MyApp\build\tmp\image --app-version 1.0.4 --input C:\dev\MyApp\build\image\app --runtime-image C:\dev\MyApp\build\image\runtime --name "My Server Admin" --main-jar libs\MyApp-1.0.4.jar --main-class my.domain.serveradmin.MyServerAdminApp --resource-dir src/main/deploy/package/windows --icon "src/main/deploy/package/windows/My Server Admin.ico" --description "My Server Administration Application" --vendor "My Company" --copyright "Copyright (c) 2015-2020 My Company Corp." --dest C:\dev\MyApp\build\application
- duplicates
-
JDK-8255095 Self contained app produced with JPackage thrown access violation exception
- Closed
-
JDK-8252828 Packaged application dies with EXCEPTION_ACCESS_VIOLATION in jimage.dll
- Closed
- relates to
-
JDK-8244495 Some jlink tests crash on Windows after JDK-8237750
- Resolved
-
JDK-8278753 Runtime crashes with access violation during JNI_CreateJavaVM call
- Resolved
-
JDK-8252828 Packaged application dies with EXCEPTION_ACCESS_VIOLATION in jimage.dll
- Closed
-
JDK-8255095 Self contained app produced with JPackage thrown access violation exception
- Closed