Most probable! Your ref [1] states fix for that is Gradle #6170, which was resolved and merged after 4.9 was release. I'll test again when 4.10 is out.
/Lennart > 23 aug. 2018 kl. 17:40 skrev Kevin Rushforth <kevin.rushfo...@oracle.com>: > > Maybe you hit Gradle #3468 [1], which I discovered as reported in JDK-8193288 > [2]? > > -- Kevin > > [1] https://github.com/gradle/gradle/issues/3468 > <https://github.com/gradle/gradle/issues/3468> > [2] https://bugs.openjdk.java.net/browse/JDK-8193288 > <https://bugs.openjdk.java.net/browse/JDK-8193288> > > > On 8/23/2018 6:36 AM, Lennart Börjeson wrote: >> I stopped my gradle demons (I had one for each JDK I'm testing) and after >> restart, everything works with either Java 10 or 11, and both openjfx >> 11-ea+19 and 11-ea+23 works now. >> >> My "real" application I'm porting to java11+openjfx also runs OK. >> >> (Oh well, just another gradle oddity then.) >> >> So, now you can update your samples to 11-ea+23 with confidence! >> >> Thanks for the help. >> >> >> Best regards, >> >> /Lennart >> >>> 23 aug. 2018 kl. 15:09 skrev Johan Vos <jo...@lodgon.com >>> <mailto:jo...@lodgon.com>>: >>> >>> The fact that you fallback to SW indicate ES2 failed to initialize indeed. >>> I checked and merged your PR, and it runs locally fine for me on mac. >>> >>> As Kevin said, can you add javafx.verbose to true, as well as >>> -Dprism.verbose=true ? >>> >>> Thanks for testing, these quirks are the ones we have to fix now :) >>> >>> - Johan >>> >>> Op do 23 aug. 2018 om 14:43 schreef Kevin Rushforth >>> <kevin.rushfo...@oracle.com <mailto:kevin.rushfo...@oracle.com>>: >>> >>> > at >>> > javafx.graphics/com.sun.prism.sw.SWPipeline.getDefaultResourceFactory(SWPipeline.java:82) >>> >>> This suggests that there may be some problems loading the native libs. >>> Can you try running with '-Djavafx.verbose=true' ? Johan might have >>> other suggestions. >>> >>> -- Kevin >>> >>> >>> On 8/23/2018 2:27 AM, Lennart Börjeson wrote: >>> > After upgrading to the latest maven artefacts (11-ea+23) from the >>> > previous (11-ea+19), I get the following error when I try to run the >>> > javafx11sample hello3d from gradle: >>> > >>> >> Task :run >>> > RenderJob.run: internal exception >>> > java.lang.ArrayIndexOutOfBoundsException: 0 >>> > at java.base/java.util.Arrays$ArrayList.get(Arrays.java:4351) >>> > at >>> > java.base/java.util.Collections$UnmodifiableList.get(Collections.java:1306) >>> > at >>> > javafx.graphics/com.sun.glass.ui.Screen.getMainScreen(Screen.java:61) >>> > at >>> > javafx.graphics/com.sun.prism.sw.SWPipeline.getDefaultResourceFactory(SWPipeline.java:82) >>> > at >>> > javafx.graphics/com.sun.prism.GraphicsPipeline.getDefaultResourceFactory(GraphicsPipeline.java:120) >>> > at >>> > javafx.graphics/com.sun.javafx.tk.quantum.QuantumRenderer.lambda$createResourceFactory$2(QuantumRenderer.java:161) >>> > at >>> > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) >>> > at >>> > java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) >>> > at >>> > javafx.graphics/com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>> > at >>> > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) >>> > at >>> > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) >>> > at >>> > javafx.graphics/com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:125) >>> > at java.base/java.lang.Thread.run(Thread.java:831) >>> > >>> > >>> > All context can be found at >>> > https://github.com/johanvos/javafx11samples/pull/1 >>> > <https://github.com/johanvos/javafx11samples/pull/1> >>> > <https://github.com/johanvos/javafx11samples/pull/1 >>> > <https://github.com/johanvos/javafx11samples/pull/1>> . >>> > >>> > The program runs fine when launched via maven or directly from the >>> > command line, so there must be some peculiarity concerning how gradle >>> > launches a program, but I can't figure out what. >>> > >>> > Note that I can run from gradle when I use the 11-ea+19 snapshots, so >>> > something must have changed in 11-ea+23 which causes this error. >>> > >>> > I'd really appreciate any help or insights with this. I get the same >>> > error when upgrading my real application, not just these samples, to >>> > 11-ea+23. >>> > >>> > This is on a Mac, BTW. >>> > >>> >> >
