-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows binaries don't include MS Visual Studio 2017 redistributables needed for OpenJFX #116
Comments
@lhochet Thanks for bringing this up. We'll verify this and update the issue when we have more information on a fix. |
Interesting, so, I was able to run your program successfully on a Windows 10 Pro system. The system had VS 2019 installed, however. After uninstalling it, the program still ran. We're setting up a new instance of Windows Server 2008 that never had Visual Studio installed to try it there. @lhochet, can you paste a link to where you downloaded Corretto? Also, what version are you using?
|
The issue has been tested at
|
Apologies |
I had the same issue on a clean Windows 7 up-to-date machine. For information, everything was working with corretto8-u202.
|
I also run into this issue. To run JavaFX applications with Corretto 8.212.04.2, the MSVC 2015 c++ runtime must be installed, otherwise the previously mentioned errors occurs. As a reference ZuluFX includes the necessary DLL:s (including |
8u222 fixes it for me. |
yes, this has been fixed in https://github.com/corretto/corretto-8/releases/tag/8.222.10.3 |
On Windows (tried on a clean Windows 7 and Windows 10 1809),
a JavaFX application fails to start with this error:
C:\dev>java -cp cls test.JavaFXApplication1
Graphics Device initialization failed for : d3d, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
at com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280)
at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:221)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:248)
at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)
at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)
at com.sun.javafx.application.LauncherImpl.launchApplicationWithArgs(LauncherImpl.java:337)
at com.sun.javafx.application.LauncherImpl.launchApplication(LauncherImpl.java:328)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.launcher.LauncherHelper$FXHelper.main(LauncherHelper.java:767)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:94)
at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:124)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.launcher.LauncherHelper$FXHelper.main(LauncherHelper.java:767)
Caused by: java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:260)
at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)
at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)
at com.sun.javafx.application.LauncherImpl.launchApplicationWithArgs(LauncherImpl.java:337)
at com.sun.javafx.application.LauncherImpl.launchApplication(LauncherImpl.java:328)
... 5 more
The test program is
JavaFXApplication1.java
The source code for Toolkit suggests the MS Visual Studio 2017 redistributables are missing,
Adding them from Visual Studio or installing them specifically fixes the issue.
The text was updated successfully, but these errors were encountered: