JDK-8122539 : Texture must be non-null IllegalArgumentException in WebView
  • Type: Bug
  • Component: javafx
  • Sub-Component: web
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2013-12-18
  • Updated: 2015-06-17
  • Resolved: 2013-12-18
Related Reports
Duplicate :  
JDK-8097381 - [WebView] solar system web page is slow, has rendering problems and throws exceptions
Relates :  
JDK-8097381 - [WebView] solar system web page is slow, has rendering problems and throws exceptions
Description
This issue does not occur in JavaFX version 2.2 but does occur in JavaFX 8 (beta, tested against 120).

Stack trace:

java.lang.IllegalArgumentException: Texture must be non-null
	at com.sun.scenario.effect.impl.prism.PrTexture.<init>(PrTexture.java:38)
	at com.sun.scenario.effect.impl.prism.PrDrawable.<init>(PrDrawable.java:41)
	at com.sun.scenario.effect.impl.prism.ps.PPSDrawable.<init>(PPSDrawable.java:41)
	at com.sun.scenario.effect.impl.prism.ps.PPSDrawable.create(PPSDrawable.java:68)
	at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.createCompatibleImage(PPSRenderer.java:164)
	at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.createCompatibleImage(PPSRenderer.java:65)
	at com.sun.scenario.effect.impl.ImagePool.checkOut(ImagePool.java:185)
	at com.sun.scenario.effect.impl.Renderer.getCompatibleImage(Renderer.java:122)
	at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.getCompatibleImage(PPSRenderer.java:169)
	at com.sun.scenario.effect.impl.prism.ps.PPSRenderer.getCompatibleImage(PPSRenderer.java:65)
	at com.sun.scenario.effect.Effect.getCompatibleImage(Effect.java:495)
	at com.sun.javafx.webkit.prism.WCGraphicsPrismContext$ClipLayer.render(WCGraphicsPrismContext.java:1245)
	at com.sun.javafx.webkit.prism.WCGraphicsPrismContext.renderLayer(WCGraphicsPrismContext.java:154)
	at com.sun.javafx.webkit.prism.WCGraphicsPrismContext.restoreStateInternal(WCGraphicsPrismContext.java:172)
	at com.sun.javafx.webkit.prism.WCGraphicsPrismContext.dispose(WCGraphicsPrismContext.java:1585)
	at com.sun.javafx.webkit.prism.WCPageBackBufferImpl.disposeGraphics(WCPageBackBufferImpl.java:40)
	at com.sun.webkit.WebPage.paint(WebPage.java:639)
	at com.sun.javafx.sg.prism.NGWebView.renderContent(NGWebView.java:73)
	at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2043)
	at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1951)
	at com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:469)
	at com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:324)
	at com.sun.javafx.tk.quantum.UploadingPainter.run(UploadingPainter.java:132)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:129)
	at java.lang.Thread.run(Thread.java:744)
Comments
For the record, I was able to get this issue when using tinyMCE, a JavaScript based HTML editor. See http://www.tinymce.com/tryit/full.php for an example. When doing some cursory testing of it, this stack trace appears.
18-12-2013
In the absence of a test case showing it to be a different problem, I am marking it as a duplicate.
18-12-2013
The is likely the same root cause as RT-34443.
18-12-2013