Follow-up to JDK-8333374 - when testing that issue there turned out to be one more spot which produces an NPE due to low Vram Pool availability and which should probably be handled with a null check:

    java.lang.NullPointerException: Cannot invoke "com.sun.prism.d3d.D3DRTTexture.contentsUseful()" because "rtt" is null
        at javafx.graphics@24-internal/com.sun.prism.d3d.D3DResourceFactory.createPresentable(D3DResourceFactory.java:383)
        at javafx.graphics@24-internal/com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.java:81)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
        at javafx.graphics@24-internal/com.sun.javafx.tk.RenderJob.run(RenderJob.java:58)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at javafx.graphics@24-internal/com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:126)
        at java.base/java.lang.Thread.run(Thread.java:1570)

To verify, check the WebViewAnimationTest.java attached to JDK-8333374 and switch scenes a lot - sooner or later it should appear. Sometimes adjusting the memory to some different low value (ex. 50m or 45m) might help.