NullPointerException at com.sun.scenario.effect

Question

Hi to all
I meet this exception in my app. At the screen it seems like lost links to my graphics(no rendering some nodes)
Are there some one to meet that exception too?
java.lang.NullPointerException
        at com.sun.scenario.effect.impl.prism.ps.PPSDrawable.create(Unknown Sour
ce)
        at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.createCompatibleIma
ge(Unknown Source)
        at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.createCompatibleIma
ge(Unknown Source)
        at com.sun.scenario.effect.impl.ImagePool.checkOut(Unknown Source)
        at com.sun.scenario.effect.impl.Renderer.getCompatibleImage(Unknown Sour
ce)
        at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.getCompatibleImage(
Unknown Source)
        at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.getCompatibleImage(
Unknown Source)
        at com.sun.scenario.effect.Effect.getCompatibleImage(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.renderOpacity(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.BaseNode.render(Unknown Source)
        at com.sun.javafx.sg.prism.NGGroup.renderContent(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.BaseNode.render(Unknown Source)
        at com.sun.javafx.sg.prism.NGGroup.renderContent(Unknown Source)
        at com.sun.javafx.sg.prism.NGRegion.renderContent(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.BaseNode.render(Unknown Source)
        at com.sun.javafx.sg.prism.NGGroup.renderContent(Unknown Source)
        at com.sun.javafx.sg.prism.NGRegion.renderContent(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.prism.NGNode.doRender(Unknown Source)
        at com.sun.javafx.sg.BaseNode.render(Unknown Source)
        at com.sun.javafx.tk.quantum.ViewPainter.doPaint(Unknown Source)
        at com.sun.javafx.tk.quantum.AbstractPainter.paintImpl(Unknown Source)
        at com.sun.javafx.tk.quantum.PresentingPainter.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at com.sun.prism.render.RenderJob.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Unknow
n Source)
        at java.lang.Thread.run(Unknown Source)

Answer 1

I think there are bugs in the underlying texture handling that are scheduled to be fixed for JavaFX 3.0 which might cause this issue. If that is in fact your issue, I'm not sure what the correct workaround is (perhaps forcing a software pipeline - which I don't know how to do - or simplifying your graphics processing).
I think the jira issue to track this is:
http://javafx-jira.kenai.com/browse/RT-15516
"image data associated with cached nodes that are removed from a scene are not aggressively released"
Essentially I think the issue is that texture memory on the video card is used up because the unused cached nodes are not aggressively garbage collected.
I'd advise trying to create a simple test case to reproduce it (I know that might be difficult...) and post your test case (or your app if you can't create one) with reproduction instructions to http://javafx-jira.kenai.com. Although maybe even just posting the stack trace to jira will be enough for the developers to verify that the issue is a duplicate of RT-15516.
I created a couple of seemingly unrelated jiras which ended up being classed as duplicates of the above jira.
In both cases I was animating large graphics at high speeds.